Zoltan Kochan
aa8d0ab9af
Add task concurrency groups to pnpm v12. A task in pnpm-workspace.yaml names a `concurrencyGroup`, and `concurrencyGroups` gives each group a limit: at most that many tasks of the group run at once on the machine, counted across every pnpm process. A task past the limit waits for a running one to finish and prints who holds the slots. A group's pool is N slot files under `<stateDir>/run-slots/<group>/`. A task takes an exclusive advisory lock on one in `run_stages` and holds it for every stage of its script, so the single-project run, the recursive run, and the tasks a `pnpm pipeline` runs in-process are all counted, each project's task separately. The operating system releases the lock when the holder ends, however it ends, so a killed holder never leaves a stale slot. `pnpm exec` names no task and is not gated. A holder lists its group in `PNPM_HELD_CONCURRENCY_GROUPS` for the scripts it spawns. A nested `pnpm run` of a task in the same group runs under the slot its parent holds, which is what keeps a script that calls `pnpm run` from waiting on itself under a limit of one. `concurrencyGroups` merges entry by entry across the configuration layers, so a machine can lower one group's limit through `PNPM_CONFIG_CONCURRENCY_GROUPS` without restating the rest. Every process that is meant to be counted has to start as `pnpm <script>`, so the root manifest gains scripts that wrap the just recipes and node scripts (`test:rust`, `test:rust-affected`, `test:rust-smoke`, `check:rust`, `lint:rust`, `ready:rust`, `pre-push:rust`), the pre-push hook runs its Rust checks through one, and the agent guide, the testing-changes skill, and the contributing guide name the pnpm scripts first. This repository's own task declarations wait for a pnpm release that knows the field: the pinned CLI rejects an unknown task setting, so adding `concurrencyGroup` to pnpm-workspace.yaml now would break every command for it.
简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro
Fast, disk space efficient package manager:
- Fast. Up to 2x faster than the alternatives (see benchmark).
- Efficient. Files inside
node_modulesare linked from a single content-addressable storage. - Great for monorepos.
- Strict. A package can access only dependencies that are specified in its
package.json. - Deterministic. Has a lockfile called
pnpm-lock.yaml. - Works as a Node.js version manager. See pnpm runtime.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- Experimental Rust port. Includes pacquet, an experimental port of the CLI written in Rust.
- See the full feature comparison with npm and Yarn.
To quote the Rush team:
Microsoft uses pnpm in Rush repos with hundreds of projects and hundreds of PRs per day, and we’ve found it to be very fast and reliable.
Platinum Sponsors
|
|
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
|
|
| ⏱️ Time.now |
Support this project by becoming a sponsor.
Background
pnpm uses a content-addressable filesystem to store all files from all module directories on a disk. When using npm, if you have 100 projects using lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be stored in a content-addressable storage, so:
- If you depend on different versions of lodash, only the files that differ are added to the store.
If lodash has 100 files, and a new version has a change only in one of those files,
pnpm updatewill only add 1 new file to the storage. - All the files are saved in a single place on the disk. When packages are installed, their files are linked from that single place consuming no additional disk space. Linking is performed using either hard-links or reflinks (copy-on-write).
As a result, you save gigabytes of space on your disk and you have a lot faster installations!
If you'd like more details about the unique node_modules structure that pnpm creates and
why it works fine with the Node.js ecosystem, read this small article: Flat node_modules is not the only way.
💖 Like this project? Let people know with a tweet
Getting Started
Benchmark
pnpm is up to 2x faster than npm and Yarn classic. See all benchmarks here.
Benchmarks on an app with lots of dependencies:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.