Ayush SinghandZoltan Kochan
a8ade4902f
The shell emulator's bundled parser reads `$NAME` but not `${NAME}`, so
every braced form reached the script as literal text.
Rewrite the braced forms the parser has an equivalent for into `$NAME`
references before parsing: `${NAME}`, `${NAME:-word}`, `${NAME-word}`,
`${NAME:+word}` and `${NAME+word}`. Only the script's own text is ever
rewritten. A parameter that has a value becomes a `$NAME` reference the
shell expands after parsing, so a value holding shell punctuation cannot
turn into a command, a redirection, or a substitution, and a default
`word` keeps the quoting the script gave it. Forms no `$NAME` reference
can stand in for, `${NAME:=word}` and `${NAME:?word}` and `${#NAME}` and
`${NAME%suffix}` among them, are left verbatim rather than evaluated
wrongly.
An expansion glued to more of the same word is closed off with an empty
string, because `$NAME` would otherwise swallow the text after it.
Which side of `${NAME:-word}` and `${NAME:+word}` is taken is read from
the environment the shell starts with, so a parameter assigned by an
earlier command in the same script is not seen. Plain `${NAME}` resolves
at run time and has no such limit.
Fixes pnpm/pnpm#14814
---------
Co-authored-by: Zoltan Kochan <z@kochan.io>
简体中文 | 日本語 | 한국어 | 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.