Zoltan KochanandClaude Opus 5.5
6d736a02a8
pnpm v12 resolved `pnpm add <pkg>` without a version, and a version-less `npm:` or `jsr:` dependency, to the `latest` dist-tag even when the `tag` setting named another one. pnpm v11 reads `tag` from pnpm-workspace.yaml, the global config, `PNPM_CONFIG_TAG`, and `--config.tag`, and threads it as `defaultTag` into `parseWantedDependencies` (installSome.ts) and the resolution context (createResolutionContext.ts). `Config` now carries `tag`, read from the same layers, with `Config::default_tag` falling back to `latest`. A brand-new `add` with no version resolves a non-default tag the way an explicit `add <pkg>@<tag>` does, so the picked version is also locked. A `jsr:` add and the install resolver take the same default. `dlx`, `add --config`, `update --latest`, and `outdated` keep `latest`, as they do in v11. Tested with e2e tests for the yaml setting, `--config.tag`, and a version-less `npm:` alias, each seen to fail with `default_tag` forced to `latest`, plus config unit tests for apply, override, reset, and the resolved projection. Part of pnpm/tasks#191 Co-Authored-By: Claude Opus 5.5 <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.
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.