3acb421adf
pnpr's access-control declaration is now pnpr-native, matching the already-native routing config. Token grammar: only the $-sigiled built-ins ($all, $authenticated, $anonymous) are recognized; verdaccio's @-prefixed and bare alias spellings are rejected at config load with a did-you-mean error, and the $ namespace is reserved so a typo'd built-in cannot silently become a username that admits nobody. Access lists and member lists no longer whitespace-split: a YAML scalar is one token, multi-token lists are YAML sequences, and an empty-string value is an error pointing at [] or omission. Teams: the global groups: block is replaced by registry-scoped teams. Each hosted or upstream registry declares its own teams: map and references it from its access lists as team:<name>; a bare token is a username only. This closes the escalation where open registration let anyone claim a username equal to a group name and inherit its grants, and it makes cross-registry reuse explicit (YAML anchors) instead of a global namespace. group:<name> gets a pointer at team:<name>, unknown <type>: prefixes are rejected (htpasswd forbids ':' in usernames), and an undeclared team reference is a startup error listing the declared teams. team: references are resolved to member sets at config load, so access-list evaluation still needs only the caller's identity: Identity drops its groups field and route classification, search, and the resolver are untouched. The removed top-level groups: block is rejected loudly, like the removed top-level packages: block, because silently dropping it would change who may reach what on upgrade.
简体中文 | 日本語 | 한국어 | 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.