Practice Turborepo-specific vocabulary: pipeline configuration, remote cache hit rates, affected packages, pruned output, and dependency graph inference.
0 / 5 completed
1 / 5
'The build is ___ — it didn't re-run any tasks.' Which word is missing?
In Turborepo, when a task's inputs haven't changed, it's 'cached' — Turborepo replays the previous output instead of re-running the task, saving build time.
2 / 5
'Remote cache ___ rate is 87%.' Which noun fits?
'Cache hit rate' measures the percentage of tasks resolved from cache rather than re-executed. An 87% remote cache hit rate means significant CI time savings.
3 / 5
'Turborepo ___ the dependency graph from package.json.' Which verb fits?
Turborepo 'infers' the dependency graph automatically by reading the workspaces and dependencies declared in package.json files — no manual graph configuration required.
4 / 5
What does 'prune output' mean in Turborepo?
'turbo prune' creates a pruned copy of the monorepo containing only the packages needed for a specific app — useful for creating lean Docker images.
5 / 5
In Turborepo's pipeline, what does it mean when a task 'depends on ^build'?
The '^' prefix in Turborepo pipeline config means 'run this task in all dependencies first'. So 'dependsOn: ["^build"]' means: build all packages this package depends on before building this one.