turborepo

Add scripts to each package's package.json, then register tasks in root turbo.json with dependsOn and outputs. Root package.json should only delegate via turbo run commands, never contain task logic itself.

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 checkout uses fetch-depth of at least 2 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. Use --summarize or --dry to inspect hash inputs and identify what invalidates 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 build for same-package task sequencing like test depending on build.

Always use turbo run in package.json scripts, CI workflows, and any committed code. The turbo shorthand is intended only for one-off interactive 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.