Zoltan Kochan
7befc73efb
A `file:*.tgz` dependency's name, version, and dependencies live only in the archive's own `package.json`. The local resolver left `manifest` unset for the tarball branch, so `build_pkg_id_with_patch_hash` had no name to prefix and emitted the bare `file:<path>` as the dep path. That parses as no lockfile key, and `build_packages_and_snapshots` dropped it with a silent `continue` — the install reported success while writing no `packages:` / `snapshots:` row and linking a dangling symlink into a virtual-store directory that was never created. Read the archive during resolution, as the tarball resolver already does for remote tarballs and the git resolver for git deps: `pacquet-tarball` grows `read_local_tarball_metadata`, which hashes the file and reads its bundled `package.json` in one pass, replacing the resolver's hash-only read. Nothing is written to the store — the install pass addresses a `file:` tarball's store-index row by its `<name>@file:<path>` dep path, not by the `<name>@<version>` a resolve-time extraction could key, so such a row would never be read. With the name in scope the dep path becomes `<name>@file:<path>`, both lockfile blocks are emitted, the tarball's own dependencies are walked (they were dropped entirely before), and the install summary prints the version instead of the raw specifier. The lockfile is byte-identical to pnpm 11's for the same manifest. The manifest is borrowed out of the decompressed archive buffer rather than read through the tar entry, so an entry header can't size an allocation; the offset/size arithmetic both call sites need is extracted into `tar_entry_payload`. Reading the manifest puts its `name` into the dep path and into a `node_modules/<name>` directory, so the shapes that used to fail silently are refused the way pnpm refuses them: a `package.json` that isn't valid JSON raises `ERR_PNPM_TARBALL_EXTRACT`, one that names no package raises `ERR_PNPM_MISSING_PACKAGE_NAME`, and one whose name isn't a valid npm name raises `ERR_PNPM_INVALID_DEPENDENCY_NAME`. Degrading to "no manifest" is right for the extraction path, whose consumers re-read from disk, but here the manifest is the package's only source of identity, so clearing it reproduces the bug above. An archive with no `package.json` at all stays tolerated, matching pnpm, which synthesizes a name from the alias. Telling that apart from a nameless manifest needs more than a `None`, so the reader reports whether a root `package.json` was present. pnpm 11 already handles `file:` tarballs correctly (it reads the manifest from the fetch, and resolves and fetches together), so this needs no TypeScript counterpart. Closes pnpm/pnpm#13379.
简体中文 | 日本語 | 한국어 | 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.