871ca5f9b6
`pnpm add` reads a `pkg:` selector as the Package URL specification defines it and routes it to the ecosystem its type names: npm to package.json, cargo to Cargo.toml, and pypi to pyproject.toml. Each purl is rewritten into the selector that ecosystem's own protocol already takes, so it inherits that path's flags, defaults, and errors instead of growing a second set. Every decoded component is validated before the pieces are joined back together. A name followed by a spec is how pnpm spells an npm alias, so a name or a version carrying a decoded at-sign or colon would otherwise redirect the install to another package. Qualifiers and subpaths are rejected rather than dropped: a repository_url qualifier or a subpath that pnpm ignores installs something other than what the selector names. AddArgs::package_names now holds the selectors the npm add path receives rather than the ones argv carried, which is what lets a purl reach the --global and --config forms as well. AddPipeline keeps only the selectors routed to another ecosystem, so the split has a single home, and dispatch_install::add delegates that split to a named step to stay within the local-binding limit perfectionist enforces. A purl always names a package to install. pnpm add node@22.0.0 records a runtime and pnpm add npm@11.0.0 records the project's package manager, both from a bare name a person typed, so the package-manager and runtime recognition skips a selector a purl was rewritten into. That mark belongs to the request rather than to its text. package_names holds AddRequest values, each carrying its own selector and whether a purl was rewritten into it, so two requests that normalize to one selector keep their own meanings and no second list has to be matched against or kept in sync. A rejected selector is quoted back by what it decodes to, because an encoded separator would otherwise hide a user:pass@ authority from a check made on the raw text. What decoding leaves unreadable to that check is stopped at instead: a colon followed by an at-sign is how a URL spells userinfo, and nothing pnpm installs pairs the two past its protocol, so no list of the characters that can sit between a scheme and its slashes has to be complete. --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Zoltan Kochan <z@kochan.io>
简体中文 | 日本語 | 한국어 | 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.