Close the four CLI-surface differences left over from pnpm/pnpm#13315 after pnpm/pnpm#13359 and pnpm/pnpm#13375 landed the other two. Three land in the Rust engine. The `Scope:` line arrives via a new `pnpm:scope` channel and a port of `reportScope.ts`; pnpm gates it on the command being one that reports scope *and* the run being workspace-wide, and since the engine's recursive-by-default set is narrower than pnpm's, that conjunction is computed at dispatch and seeded into the reporter. The event is emitted where the counts already exist — the `--filter` resolution and the installer's workspace walk — so no install pays for a second directory walk. A `sharedWorkspaceLockfile: false` plan reports once for the whole selection rather than once per child install, which would otherwise overwrite the filtered count with the workspace total. The second is the `allowBuilds` placeholder an install writes for a build it blocked, which pnpm/pnpm#13375 taught the engine to read but not yet to write. The third is the elapsed time on a cache-satisfied lockfile verdict. The fourth goes the other way. The store block a first install prints is unreachable in the TypeScript CLI: `reportContext` needs `pnpm:package-import-method`, which only `@pnpm/fs.indexed-pkg-importer` emits, and that runs inside a `@pnpm/worker` thread whose logger never reaches the reporter. The main process already receives the import method back from the worker, so it is reported from there instead. Reporter globals are now seeded before the pre-command checks. They are `OnceLock`s and the pre-command checks emit, so whatever fired first was locking in unset values. Closes pnpm/pnpm#13315
jsr: and named-registry package names (empty scope/name, path separators) (#12677)
简体中文 | 日本語 | 한국어 | 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.