turborepo

Define tasks in the root turbo.json tasks object with dependsOn and outputs, for example "build": { "dependsOn": ["^build"], "outputs": ["dist/**"] }. Add the actual scripts to each package's package.json and have the root package.json delegate with "turbo run build".

Use the --affected flag, for example "turbo run build --affected", which compares against main and includes dependents of changed packages. Set TURBO_SCM_BASE to compare against a different base branch such as origin/develop.

Cache misses usually come from a missing outputs key on 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.

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.

The caret form ^build runs the build task in dependency packages first, while plain build runs it in the same package first. A specific package's task can be targeted with the pkg#task syntax such as web#build.

Yes, but strict mode filters variables to only those declared in env or globalEnv. Add CI variables like GITHUB_TOKEN to globalPassThroughEnv so they are available at runtime without affecting cache hashes.