e9be2b9fbe
A task the recursive runner dispatches holds every script a RegExp selector matched in that package, and it ran them in sequence. `RunArgs::run` has started them together since it gained `run_selected_scripts`, and pnpm 11 fans them out through its `limitRun` limiter, so the recursive Rust path was the odd one out. `run_project` now picks between a concurrent and a sequential mode the way the single-project path does, sharing the verdict bookkeeping through `ScriptRunState` so both record the same transitions. Running several scripts per task breaks the equivalence the scheduler relied on: capping dispatched tasks caps running scripts only while a task runs one script at a time. `ScriptBudget` restores it. It is one counting semaphore for the whole run, sized by `script_concurrency` over every matched script, and each script holds a permit while it runs. A permit is never held while waiting for another, so the budget cannot deadlock, and single-script tasks are unaffected: the outer task cap and the budget are then the same number and no script ever waits. Two consequences of the concurrency needed handling: - A task's own failure outranks the cancellation it causes. Under `--bail` the failing script cancels the run, its sibling is killed, and the sibling's cancellation used to overwrite the task's verdict, because `RunOutcome::record` reads `cancelled` before `failed`. The run then reported ERR_PNPM_RECURSIVE_FAIL instead of naming the project with ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL, unlike a failure in another package. `ScriptRunState::cancelled_script` keeps the failure. - A script must not start on a permit it won after the run was cancelled. `run_stages` returns early on `SlotOutcome::Ungated` without consulting the tracker, so such a script reached `run_script` and spawned a process that registration then killed. `start_script` returns no permit in that case, which is the guard `runRecursive.ts` applies after its own limiter on pnpm 11. Closes pnpm/pnpm#14933 --------- Co-authored-by: Zoltan Kochan <z@kochan.io> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
简体中文 | 日本語 | 한국어 | 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.