Question 1

How do I configure turbo.json outputs for caching?

Accepted Answer

List every directory a task writes, such as dist/** or .next/**, in the outputs array. For tasks that write nothing like typecheck or lint, explicitly set outputs to an empty array so Turbo does not cache the whole package.

Question 2

What is the difference between ^build and build in dependsOn?

Accepted Answer

The caret form ^build waits for the build task of upstream workspace dependencies, while bare build waits for the build task in the same package. Most tasks need ^build so dependencies compile before consumers.

Question 3

When should I set up Turborepo remote cache?

Accepted Answer

Remote cache pays off with teams of three or more developers, CI running ten or more times daily, or builds over one minute. Solo developers with local caching should skip it since setup overhead exceeds the benefit.

Question 4

Why does Turborepo keep rebuilding everything in CI?

Accepted Answer

Full rebuilds usually mean no remote cache is configured, or build artifacts are gitignored but missing from outputs. Verify outputs match what tasks actually write and pass TURBO_TOKEN and TURBO_TEAM to CI.

Question 5

When should I override the inputs field in turbo.json?

Accepted Answer

Override inputs only when a task reads files outside its package or should ignore changes to files like README.md. Over-restricting inputs is the top cause of stale-cache bugs, so omit it when in doubt.

void-turbo-pipeline-tuning

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about void-turbo-pipeline-tuning

Related Skills

typescript:build-tools

turborepo

turborepo

monorepo-ci-optimizer