turborepo

Add scripts to each package's package.json, register the task in root turbo.json with dependsOn and outputs, and make root package.json delegate via turbo run. Never put task logic in root scripts, as that defeats parallelization and caching.

Use turbo run build --affected, which compares your branch against the default branch and runs tasks in changed packages plus their dependents. Ensure your CI fetches enough git history (fetch-depth of at least 2) for the comparison to work.

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 is invalidating the cache.

The caret syntax ^build runs the build task in dependency packages first, while plain build runs it in the same package. Use ^build for build ordering across packages and pkg#task to target a specific package's task.

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

Use a turbo.json with extends ["//"] inside a package when multiple packages need different task settings, such as framework-specific outputs. This keeps root turbo.json clean and configuration close to the code it affects.