Zoltan KochanandClaude Fable 5.1
919a2ec683
* perf(napi): take the repeat-install fast path with in-memory manifests The Node-API bindings disabled both repeat-install short-circuits, because the workspace-state check judged manifest freshness by the package.json mtime, which says nothing about a manifest the caller supplied in memory and may not exist on disk at all (a Bit component directory carries no package.json). Every repeat install therefore ran the full frozen path, re-copied every file: directory snapshot, and reported them as added, so the embedder saw dependencies change on every run. Add ManifestFreshness to the check. Mtime keeps the CLI behavior. Content skips the stat and compares every importer with the wanted lockfile by content, which is the authoritative check the mtime shortcut only avoids. The bindings select Content and re-enable both short-circuits for installs; peer-issue queries stay excluded because they exist to resolve. The wanted-vs-current assertion in the content check now uses the reachable-shape comparison the frozen-tree gate already used: the current lockfile records only what the importers reach and none of the top-level keys pnpm does not define, so a wanted lockfile with an unreachable snapshot or an embedder's extension block was never equal to it and kept forcing a full install. The skipped reason is now logged at debug level. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * chore: address the first review round Keep the changeset user-facing, drop a test doc comment that narrated the test's own setup and assertions, and require the content-mode check to advance the recorded validation timestamp rather than merely hold it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs: state the plain lockfile policy's contract instead of its fields Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <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.