712fce50bc
`PackageSpecifierPlan::parse` took a `&[AddRequest]`, so every selector the npm add path reads as it was written was cloned on its way into the plan. It now takes the requests by value and moves each one. The other arms are untouched. Cargo, Python and each purl type build a new selector out of the parsed components, so none of them ever needed to own what it was handed, and a purl still mints its request through `AddRequest::from_package_url`. `IntoIterator` rather than a slice or a `Vec` because `parse` iterates once, front to back, and never indexes or asks for a length. The one production caller owns its vector and overwrites it on the next line, so `std::mem::take` hands it over at no cost, and the test call sites pass their array by value rather than by reference. Counted with a global allocator: `pnpm add lodash@4 react@18 express@4.18.2` falls from four allocations to one, the one the destination vector needs, and a lone `lodash@4` from two to one. The purl and `crate:` / `pypi:` shapes are unchanged, and no shape regresses. Behavior is unchanged, so the test asserts a pointer rather than the contents. A move leaves the heap buffer where it is, and nothing else in the suite catches a clone creeping back in. 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.