Course by Juri StrumpflohnerFrom PNPM Workspaces to Distributed CILessons
  1. 1Course Intro1m 01s
  2. 2Initialize Nx in Your Project with nx init3m 42s
  3. 3Run and Manage Tasks Efficiently Using Nx1m 56s
  4. 4Configure Cache Outputs to Handle the .next Folder2m 07s
  5. 5Create a Task Pipeline to Build Your Next app Before Serving it3m 07s
  6. 6Link an e2e Project with Its Web App Through Implicit Dependencies2m 38s
  7. 7Connect Your Workspace to Nx Cloud4m 00s
  8. 8Use Nx Commands on CI4m 43s
  9. 9Enable Read/Write Access to your Nx Remote Cache from CI1m 45s
  10. 10Debug Remote Cache misses with Nx Cloud0m 53s
  11. 11Enable Remote Caching for your Developer Machine with Nx Login1m 38s
  12. 12Speed Up CI by Running Tasks in Parallel on Different Machines2m 08s
  13. 13Run Playwright E2E Tests Faster by Parallelizing Them on CI5m 47s
  14. 14Course Outro0m 39s

Create a Task Pipeline to Build Your Next app Before Serving it

All Next.js projects usually come with these package.json scripts:

package.json
{
    ...
    "scripts": {
        ...
        "build": "next build",
        "start": "next start"
    }
}

Running next start will only work if the .next folder is present in the project's root. This folder is created when running next build.

This is a very simple use case of a task pipeline, which defines dependencies among tasks.

In this lesson we're going to create a simple task pipeline such that whenever you run next start, Nx will automatically run next build (or restore it from the cache).

← PreviousConfigure Cache Outputs to Handle the .next FolderNext →Link an e2e Project with Its Web App Through Implicit Dependencies