turborepo

Design root and per-package turbo.json files to configure a monorepo build pipeline, defining task inputs, outputs, and environment variables to establish a dependency-aware task graph.

The best way to optimize CI builds in a monorepo is to run turbo run <task> with the --affected flag, which limits task execution to only the packages impacted by recent changes, leveraging caching to skip redundant work.

Monorepo caching works by matching declared task inputs and environment variables against cached outputs, skipping redundant task execution across apps and libraries when the underlying dependency graph and inputs remain unchanged.

Yes, you can apply package-specific configurations by adding per-package turbo.json files within apps and libraries, overriding or extending the root configuration to handle individual package boundaries and custom task requirements.

You need advanced features like transit nodes in Turborepo when managing complex codebases that require precise dependency-aware task graphing across package boundaries, ensuring correct build order for interconnected apps and libraries.