turborepo

Add scripts to each package's package.json, then register the task in root turbo.json with dependsOn and outputs. Root package.json should only delegate via turbo run <task>, never contain task logic, so Turborepo can parallelize and cache per package.

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: 2 or 0) so the merge base is available.

Common causes include missing outputs keys for file-producing tasks, environment variables not declared in env, or .env files absent from inputs. Debug with --summarize or --dry to inspect hash inputs and identify what changed between runs.

^build runs the build task in dependency packages first, while build (without caret) runs it in the same package first. Use ^build for build ordering across packages and plain build for same-package prerequisites like test depending on build.

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.

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.