turborepo

Use the turbo run command to execute task pipelines instead of root scripts. This orchestrates builds across apps and packages, leveraging intelligent caching and parallel task execution defined in your turbo.json.

Build caching in a Turborepo monorepo works by storing task outputs and skipping redundant work across packages. It supports shared caching and remote cache in CI to optimize build times and avoid reprocessing unchanged code.

The best way to run changed or affected packages in CI is by using affected-mode runs with --filter and --affected flags. This CI optimization strategy skips unaffected packages and leverages caching for faster pipelines.

You define per-package task configuration in each package, then register them in the root turbo.json. This setup supports turbo.json inheritance, allowing explicit task definitions with dependsOn and outputs across your monorepo structure.

You should use turbo run instead of root package.json scripts because it enables intelligent caching, parallel task execution, and proper dependency ordering via dependsOn. Root scripts lack the build orchestration and remote cache capabilities needed for monorepo optimization.

Enforce package boundaries when sharing code between apps by following monorepo structure best practices and configuring task pipelines. This ensures internal packages respect defined boundaries and dependencies are managed correctly during builds.