turborepo

Define a build task with dependsOn set to ["^build"] so dependency packages build first, and declare outputs like ["dist/**"] so results are cached. Add the build script to each package's package.json and delegate from root with turbo run build.

Use the --affected flag, for example turbo run build --affected, which compares your branch against the default branch and runs tasks in changed packages plus their dependents. You can customize the base with --affected-base=origin/develop.

Common causes include missing outputs keys for file-producing tasks, environment variables not declared in env, or .env files absent from inputs. Use --summarize or --dry to inspect hash inputs and identify what invalidates the cache.

Always use turbo run in package.json scripts, CI workflows, and any committed code. The shorthand turbo <task> is intended only for one-off commands typed directly in a terminal.

Add TURBO_TOKEN as a secret and TURBO_TEAM as a variable in your repository settings, then expose them as environment variables in the workflow. Also set fetch-depth to at least 2 on checkout so --affected can compute the merge base.

Root tasks (//#taskname) should only be used for work that truly cannot live in a package, such as repo-wide release scripts or Vitest Projects' //#test. Everything else should be a package task to preserve parallelization, per-package caching, and filtering.