Zoltan Kochan
3c4fa855fa
A `file:` specifier is relative to the directory of the manifest that declares it — pnpm's `parentPkg.rootDir`. The tree walk threaded the importer's `project_dir` through every depth, so a `file:` dependency of a package installed from a local directory was resolved against the importer instead. A `file:../child` in `packages/license/parent` landed on `packages/child` and the install failed with `ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND`. The children walk now derives the declaring package's directory from its directory resolution (relative to the lockfile root, absolute for `link:`-shaped ones) and hands it to each `file:` child's resolve options. It joins the per-wanted dedup key through `project_relative_cache_scope`, so two parents that declare the same relative specifier no longer share a resolution. The speculative children warm-up applies the same override, both to keep it from resolving a path that doesn't exist and so it warms the key the real resolve reads back. Once resolution was correct, the snapshot the lockfile writes for such a dependency still diverged: pacquet wrote `<name>@file:<path>` where pnpm writes the bare `file:<path>` whenever the alias equals the package's own name. The importer side already stripped that self-alias; the strip is now shared with the snapshot side, so a workspace with nested `file:` deps (vite's license fixtures) round-trips through `pnpm dedupe --check` against a pnpm-written lockfile. pnpm 11 already resolves these correctly and covers the shape with its `deep local` test, so no TypeScript change is needed. Closes pnpm/pnpm#13323
简体中文 | 日本語 | 한국어 | 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.