Practice workspaces vocabulary for npm, pnpm, and yarn: local package linking, content-addressable stores, zero-installs, symlinks, and hoisting.
0 / 5 completed
1 / 5
'The workspace package is ___ locally.' Which verb describes how packages are connected within a workspace?
Workspace packages are 'linked' — package managers create symlinks in node_modules so packages can reference each other without publishing to a registry.
2 / 5
'pnpm uses a content-___ store.' Which adjective completes this?
pnpm's 'content-addressable store' stores each package version once on disk by its content hash. All projects share the same store via hardlinks, saving gigabytes of disk space.
3 / 5
'Yarn Berry has ___-installs.' What feature allows skipping `yarn install` in CI?
Yarn Berry's 'zero-installs' feature commits the package cache to the repository (using PnP or zip archives). CI can skip the install step, using the committed packages directly.
4 / 5
'The ___ in node_modules points to packages/utils.' Which filesystem concept is used?
A 'symlink' (symbolic link) is a filesystem pointer. Workspace package managers create symlinks in node_modules so packages/utils appears there as if installed from a registry.
5 / 5
What is 'hoisting' in workspace package management?
Hoisting moves shared dependencies to the root node_modules, reducing duplication. npm and yarn (classic) hoist by default; pnpm uses a stricter non-hoisting model to prevent phantom dependencies.