Turborepo Monorepo Guide FAQs

Question 1

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

Accepted Answer

'turbo run' is the explicit command that should be used in package.json scripts, CI/CD workflows, and automated code. The shorthand 'turbo <command>' is intended only for one-off terminal commands typed by developers.

Question 2

Why shouldn't I put task logic in the root package.json?

Accepted Answer

Putting logic in the root package.json defeats Turborepo's ability to parallelize tasks effectively across the dependency graph. The root should only delegate to 'turbo run' to ensure the build system can manage execution order and caching correctly.

Question 3

How do I run only the packages affected by my changes?

Accepted Answer

Use the 'turbo run <task> --affected' flag. This automatically identifies changed files via Git and executes tasks only for those packages and their dependents, significantly speeding up development and CI cycles.

Question 4

How does Turborepo handle environment variables for caching?

Accepted Answer

Turborepo includes environment variables in its hash calculation to ensure cache integrity. You must declare variables in the 'env' or 'globalEnv' keys in turbo.json so Turborepo knows when a change in environment requires a fresh build.

Question 5

Can I use Turborepo for both internal libraries and applications?

Accepted Answer

Yes, Turborepo is designed to manage complex structures involving shared internal packages (libraries) and consumer applications (apps), providing clear boundaries and efficient build ordering between them.

Turborepo Monorepo Guide

Turborepo Monorepo Guide

주요 기능

사용 사례

주요 기능

사용 사례