turborepo

Define a build task with dependsOn set to ["^build"] so dependency packages build first, and declare outputs like ["dist/**"] so results are cached. Add the build script to each package's package.json, and let the root package.json delegate with "turbo run build".

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. For custom comparisons, use --filter with git range syntax like --filter=...[origin/main].

Cache misses usually come from missing outputs declarations, 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 globalDependencies is not overly broad.

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 by humans or agents.

^build runs the build task in dependency packages first, while plain build runs it in the same package. Using "build" without the caret in a build task's dependsOn creates a self-reference and is a common configuration mistake.

Yes, set TURBO_TOKEN as a secret and TURBO_TEAM as a variable in your workflow environment to enable Vercel Remote Cache. Use fetch-depth of at least 2 on checkout so --affected can compute the merge base.