turborepo

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

Use the --affected flag: turbo run build test lint --affected. It compares your branch against the default branch and runs tasks in changed packages plus their dependents. Customize the base with --affected-base=origin/develop.

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, or use --force to bypass cache entirely.

Always use turbo run in package.json scripts, CI workflows, and any committed code. The shorthand turbo <task> is only intended for one-off interactive terminal commands typed directly by humans.

^build runs the build task in dependency packages first, while plain build runs it in the same package. Use pkg#task syntax to depend on a specific package's task, such as "deploy": { "dependsOn": ["web#build"] }.

Yes, Turborepo works with GitHub Actions using checkout with fetch-depth of at least 2 for --affected. Set TURBO_TOKEN and TURBO_TEAM secrets for remote caching, and run turbo run build test lint --affected for efficient PR builds.