Turborepo Monorepo Expert FAQs

Question 1

Is having a large number of environment variables in my config an anti-pattern?

Accepted Answer

No. Explicitly declaring even 50+ variables in the 'env' array is considered a best practice because it ensures your build hashes are accurate and your cache is reliable.

Question 2

What is the difference between 'turbo' and 'turbo run'?

Accepted Answer

You should always use 'turbo run' when writing scripts in package.json or CI pipelines. The shorthand 'turbo <task>' is intended strictly for interactive terminal use by humans.

Question 3

How do I run tasks only for packages that have changed?

Accepted Answer

Use the '--affected' flag. This is the primary way to run tasks for changed packages and their dependents by comparing your current state against a base branch.

Question 4

Why should I use package tasks instead of root tasks?

Accepted Answer

Root tasks defeat Turborepo's parallelization capabilities. Defining tasks in each individual package allows Turbo to orchestrate and run them concurrently based on the dependency graph.

Question 5

How can I debug why my cache isn't working as expected?

Accepted Answer

Use the '--summarize' or '--dry' flags to inspect hash inputs. Common issues include missing 'outputs' keys in turbo.json or undeclared environment variables that affect the build.

Turborepo Monorepo Expert

주요 기능

사용 사례

Turborepo Monorepo Expert

주요 기능

사용 사례