Practice English vocabulary for monorepo tooling concepts: workspaces, lockfiles, build systems, and shared configuration.
0 / 5 completed
1 / 5
What does 'the workspace package is auto-linked' mean?
In monorepo workspace setups (npm/yarn/pnpm workspaces), packages within the repo are automatically linked so you can import them as if they were installed from npm.
2 / 5
A developer says 'pnpm's strict lockfile prevents phantom dependencies'. What is a phantom dependency?
Phantom dependencies occur when a package is accessible because it was hoisted to node_modules by a parent package, even though it is not declared in your own package.json. pnpm's strict mode prevents this.
3 / 5
What does 'the build system only rebuilds affected packages' mean?
Modern monorepo build tools like Turborepo and Nx use dependency graphs and caching to skip rebuilding packages that have not changed, drastically reducing build times.
4 / 5
What is meant by 'the shared ESLint config is in the root'?
Monorepos often place shared tooling configs (ESLint, Prettier, TypeScript base) in the root so all packages inherit the same rules, with packages able to extend or override as needed.
5 / 5
What does 'workspace protocol (workspace:*)' mean in a monorepo dependency declaration?
The 'workspace:*' protocol (used by pnpm and Yarn) tells the package manager to always resolve the dependency from the local workspace, ensuring you always use the local source during development.