Practice workspaces vocabulary for npm, pnpm, and yarn: local package linking, content-addressable stores, zero-installs, symlinks, and hoisting.
0 / 10 completed
1 / 10
'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 / 10
'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 / 10
'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 / 10
'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 / 10
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.
6 / 10
Sarah from the frontend team just commented on your PR: 'I'm seeing some unexpected builds after you added the `react-ui` workspace. It seems like changes in one package are triggering rebuilds in others. What does she likely mean when referring to 'package dependencies'?
Sarah's comment focuses on unexpected rebuilds after updating a package. This indicates that changes in one workspace are triggering updates in other dependent workspaces – demonstrating the core concept of *package dependencies* within an npm/pnpm/yarn workspace. The key is understanding how updates ripple through connected packages; option A and C are irrelevant, while D is a direct criticism.
7 / 10
During a standup meeting, Mark asks: 'How's the `auth` workspace integration coming along?' Your teammate responds, 'We're using pnpm's 'mirroring' feature to speed up installs across all workspaces.' What does 'mirroring' refer to in this context?
'Mirroring' is a key feature of pnpm workspaces. It creates a shared, localized cache of packages across all workspaces connected to the same pnpm store. This avoids redundant downloads and dramatically speeds up installation times compared to Yarn or npm, which typically download each package individually for each workspace. Options A and D are incorrect; option B describes cloning, not mirroring.
8 / 10
You're reviewing an API response from the npm registry: `{"status":"success","message":"Workspace 'my-app' successfully linked.","dependencies": {"react": "17.0.2", "axios": "0.27.2"}}`. What does this response primarily indicate?
The API response confirms a successful linking operation for your 'my-app' workspace. The `status` indicates success and the `dependencies` section shows the resolved versions of packages within that specific workspace's context. This is how npm/pnpm/yarn track dependency resolutions *within* a linked workspace, not globally across the registry.
9 / 10
David in the code review asks: 'Can you explain why we're using `package.json` files within each workspace package?' What's the fundamental reason?
Each package within an npm/pnpm/yarn workspace needs its own `package.json` file to declare its dependencies and scripts. This allows each package to be treated as an independent unit while still being able to interact with other packages in the same workspace. The `package.json` defines the runtime environment for that specific component – it's not a global configuration.
10 / 10
You're setting up a new project using pnpm workspaces. You want to ensure that changes made to the `components` package are automatically reflected in the `app` package without requiring manual reinstallation. Which feature should you primarily leverage?
pnpm's mirroring feature is specifically designed to automatically synchronize packages between linked workspaces. This eliminates the need for manual reinstallation or running `yarn install` after modifying a shared package – ensuring that changes are immediately reflected in dependent packages within the workspace.
What will I practise in "npm/pnpm/yarn Workspaces Vocabulary"?
This module focuses on Package Management — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Package Management exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around package management — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Package Management exercises?
See the Package Management hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.