Zoltan Kochan
8cdc670197
A catalog is declared in `pnpm-workspace.yaml`, so a relative path in an entry has to be measured from that directory rather than from the project that dereferences it. Catalog resolution now re-anchors a `file:` / `link:` entry on the consuming project's directory. That is the job the root-level `pnpm.overrides` rewrite already did for its own local targets, so its `LocalTarget` moves into the new `pnpm-local-spec` crate and both read from it. The shared version anchors through `pnpm_fs::relative_path`, which lexically normalizes both sides and refuses to diff across Windows path prefixes. `resolve_from_catalog` takes the anchor as a required argument, so every call site states whether it installs from the entry or only compares, displays, or re-anchors it itself. The install resolver re-anchors on the declaring manifest's directory; `pnpm dlx` renders an absolute path because it installs outside the workspace; overrides, peer ranges, `catalogMode`, `pnpm outdated`, and the published manifest read the entry as written. The lockfile's `catalogs:` snapshot keeps the entry exactly as `pnpm-workspace.yaml` writes it, and now records an entry with no version of its own at all, so editing a local entry's path invalidates the lockfile. Its `version` holds the resolved path for such an entry, taken from the lowest-sorting importer that resolves it. A `~/` path is not absolute as far as `Path::is_absolute` is concerned, so re-anchoring joined it onto the declaring file's directory and produced a path through a literal `~` component. The local resolver expands `~/` against the home directory itself and records the specifier verbatim, so such a path names the same place from every directory and is left where it is written, like an absolute one. `pnpm.overrides` shared the flaw and is fixed with it. `pnpm pack` and `pnpm publish` re-anchor a local entry on the package being exported. A `file:` dependency written directly in a project's manifest is exported unchanged and resolves from that project, so a catalog entry carrying the same text has to mean the same place rather than a path from the workspace root. Closes pnpm/pnpm#8642
简体中文 | 日本語 | 한국어 | 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.