turborepo

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

Use dependsOn with the caret syntax: "build": { "dependsOn": ["^build"] } runs build in dependency packages first. Without the caret, it refers to the same package's task. Declare scripts in each package's package.json and register tasks in root turbo.json.

Common causes include missing outputs keys for file-producing tasks, environment variables not listed in the env key, or .env files absent from inputs. Debug with --summarize or --dry to inspect hash inputs, and check that lockfiles are committed.

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

Yes. List variables in a task's env key so changes invalidate that task's cache, or use globalEnv for variables affecting all tasks. Use passThroughEnv for runtime-only variables like credentials that should not affect cache keys.

Only when a task truly cannot exist in a package, such as repo-wide release scripts or Vitest Projects' //#test. Package tasks enable parallelization, individual caching, and filtering, so they should be the default for build, lint, and test.