Zoltan Kochan
4f83ee223e
A plain lockfile key (`@scope/a@1.0.0`) records no registry, so the reuse gate read its registry from the current scope route. Routing the scope to another registry was invisible: the lockfile stayed fresh, the install went headless, and the locked versions and children were fetched from the new registry with the old integrity. The install failed where resolving against the new registry would succeed. The workspace state now records the scope routes an install resolved the lockfile under (registryRoutes). A resolving unfiltered install records the routes it ran under; a frozen or filtered install keeps the previous record while a plain key still sits under a moved route. The default registry is not recorded: switching it is routinely a mirror switch and would resolve every unscoped package again. The registry context carries those routes as the provenance of plain keys. The reuse gate reads a plain key's registry from them, so a key under a moved scope is refused, loses its pin, and resolves again from its range against the new registry. In pacquet the subtree-reuse walk also refuses a subtree holding a moved key, because a reused parent seeds its children with exact pins and only its fresh manifest carries the ranges. A plain key under a moved route marks the lockfile stale for a resolving install; --frozen-lockfile installs it as recorded. A route change is a settings drift for the repeat-install shortcut. The route: entries of registryPrefixes are redundant with the new record and are dropped (that record is unreleased). Closes https://github.com/pnpm/tasks/issues/209
简体中文 | 日本語 | 한국어 | 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.
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.