Practise vocabulary for Turborepo and Nx: workspace packages, task graphs, affected commands, and remote caching.
0 / 5 completed
1 / 5
In a Turborepo workspace, a ___ is an individual project or library that can be built, tested, or deployed independently.
A package is the unit of code organisation in a Turborepo or Nx workspace. Each package has its own package.json, can declare its own scripts, and is linked via workspace protocols.
2 / 5
When running `turbo run build`, Turborepo executes tasks in ___ order, ensuring dependencies are built before the packages that depend on them.
Turborepo uses topological order (based on the dependency graph) to determine task execution order. A package's build only runs after all its dependencies' builds complete.
3 / 5
A ___ in Turborepo or Nx occurs when the task output matches a previous run's cached output, skipping re-execution.
A cache hit means the inputs (source files, environment, dependencies) haven't changed since the last run, so Turborepo replays the cached output instead of re-running the task.
4 / 5
The `nx affected:test` command runs tests only for packages ___ by recent code changes.
Nx's 'affected' commands use the dependency graph to identify only the packages impacted by changes (compared to the base branch), dramatically reducing CI time in large monorepos.
5 / 5
A remote cache in Turborepo allows ___ builds to share cached task outputs, so each engineer benefits from CI cache results.
A remote cache (e.g., Vercel Remote Cache, self-hosted) stores task outputs so that any machine — developer laptop or CI runner — can retrieve results if the inputs match, avoiding redundant work.