Turborepo Monorepo Build System FAQs

Question 1

Why should I use 'turbo run' instead of 'turbo' in my scripts?

Accepted Answer

'turbo run' is the explicit command recommended for package.json and CI environments to ensure consistent behavior, whereas the shorthand 'turbo <task>' is designed for interactive terminal use by humans.

Question 2

What is the best way to run only changed packages in CI?

Accepted Answer

Use the '--affected' flag. This primary filtering method automatically compares your current branch against the default branch and includes all changed packages and their dependents in the task run.

Question 3

How do I fix cache misses in my Turborepo setup?

Accepted Answer

Cache misses often occur due to missing 'outputs' keys in turbo.json or undeclared environment variables. Use the --summarize flag to debug hash inputs and ensure all dependencies are correctly mapped.

Question 4

How does Turborepo handle environment variables?

Accepted Answer

Turborepo uses a strict mode that filters environment variables. You must explicitly declare variables used by your tasks in the 'env' or 'globalEnv' keys of turbo.json to ensure they are included in cache fingerprinting.

Question 5

Should I create tasks in the root package.json?

Accepted Answer

No, you should avoid Root Tasks. Always define tasks in individual package.json files and register them in the root turbo.json to allow Turborepo to orchestrate parallel execution effectively.

Turborepo Monorepo Build System

Turborepo Monorepo Build System

Key Features

Use Cases

Key Features

Use Cases