turborepo

Add the build script to each package's package.json, then register the task in root turbo.json with dependsOn set to ["^build"] and outputs like ["dist/**"]. The root package.json should only delegate via "turbo run build".

Use the --affected flag, for example "turbo run build --affected", which compares against the default branch and includes dependents. Customize the base with --affected-base=origin/develop.

Cache misses usually come from changed environment variables, untracked .env files, lockfile updates, or turbo.json edits. Run with --summarize and compare two run summaries to identify which hash input changed.

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.

Turborepo does not load .env files itself; your framework does. To keep caching correct, list the variables in the task's env key and add the .env files to the task's inputs array.

Avoid --parallel because it bypasses the dependency graph and can cause race conditions. Instead configure dependsOn correctly, or use transit nodes for tasks that need parallel execution with proper cache invalidation.