turborepo

To speed up monorepo builds, configure cached, dependency-aware task execution using turbo.json. Define package scripts for build, lint, and test, then delegate from the root so work runs in parallel and avoids redundant runs.

Correct build caching requires defining inputs, outputs, and env in your turbo.json task configuration. This explicitly declares what files and environment variables affect a task's cache key and what artifacts are restored upon a cache hit.

Running only changed packages in CI uses the --affected or --filter flags with Turbo commands. This selective execution targets specific subsets of your monorepo, preventing unnecessary builds and dramatically reducing pipeline runtime.

You can share monorepo cache artifacts across CI runs by enabling remote cache support. This allows your pipeline to fetch cached outputs from a shared remote store, dramatically reducing CI runtimes after the first run.

Structuring task pipelines requires defining dependency relationships using the dependsOn property within turbo.json. This coordinates deterministic package task orchestration, allowing independent tasks like lint and test to execute in parallel.

You should not rely on task caching when outputs or environment variables are incorrectly hashed or undefined. If cache keys do not accurately reflect task inputs, cached artifacts become stale and produce inconsistent build results.