Zoltan Kochan
4d58dae67f
`supportedArchitectures` stood for the cross product of its `os`, `cpu` and `libc` axes, which cannot express the platform set a workspace usually ships: Linux x64, macOS arm64 and Windows x64 is three platforms, but as axes it is six, including the three nobody asked for. The setting now also reads as a list of the platforms themselves. An entry parses either as pnpm's own `<os>-<cpu>[-<libc>]` spelling, the one `pnpm pack-app --target` already takes, or as the Rust target triple of the same machine, the one uv and the rest of the Python tooling use. Both canonicalize to one value, so two spellings of a platform are one platform rather than two. On Linux the C library field also carries a Python wheel ABI baseline, as in `linux-x64-manylinux_2_28`, which is the Python-specific dimension the axes have nowhere to put. A Linux platform that names no C library is the glibc platform, as `linux-x64` means wherever else it is written. This lets `python.platforms` go. It named the same thing in a spelling of its own, in a per-ecosystem setting, while the setting that says which platforms an install prepares for was already there. `pylock.toml` is now resolved for the platforms `supportedArchitectures` names, so a workspace declares its platforms once for its npm and its Python dependencies both. The axes keep their meaning for a project that writes them, Python included, where they stand for every platform they cross into. The optional-dependency check judges a listed platform as a whole rather than an axis at a time: `[linux-x64, darwin-arm64]` refuses a package built for darwin x64, where the axes take it because each axis matches on its own. The dlx cache key and the runtime-archive selector read the new form too, the latter preferring the listed platform this machine is over mixing one axis with another. `python.platforms` and `python.pythonVersions` have not been released, so this reuses their pending changeset rather than adding a migration. Related to pnpm/pnpm#14945
简体中文 | 日本語 | 한국어 | 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.