0ad32ea5a2
A scoped dependency's `node_modules/@scope/name` link path is built by joining the whole `@scope/name` alias as one segment. Rust's `Path::join` appends segments verbatim (unlike Node's `path.join`, which normalizes), so the `/` inside the alias survived into an otherwise `\`-separated Windows path and reached `CreateSymbolicLinkW`, which rejects forward-slash paths — the long store paths reach it in verbatim `\\?\` form where `/` is a literal filename byte — with `ERROR_DIRECTORY` (os error 267), aborting the install. This is the same failure class as the global-virtual-store slot-path fix in https://github.com/pnpm/pnpm/pull/12976, which normalized the slot suffix at its construction sites. Rather than chase every join site, rewrite paths to native separators at the symlink writer's own choke points: `symlink_dir` (covering the hoisted linker's direct calls) and `force_symlink_dir`'s entry (so its read_link / remove_dir / rename / create_dir_all retry steps all see a native path too). The rewrite only allocates when a `/` is actually present and is a no-op on Unix. The TypeScript CLI is unaffected: Node's `path.join` already normalizes separators on Windows, so no counterpart change is needed. Co-Authored-By: Claude Opus 4.8 (1M context) <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.