pnpm 10.9
Minor Changes
-
Added support for installing JSR packages. You can now install JSR packages using the following syntax:
pnpm add jsr:<pkg_name>
or with a version range:
pnpm add jsr:<pkg_name>@<range>
For example, running:
pnpm add jsr:@foo/bar
will add the following entry to your
package.json
:{ "dependencies": { "@foo/bar": "jsr:^0.1.2" } }
When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
{ "dependencies": { "@foo/bar": "npm:@jsr/foo__bar@^0.1.2" } }
Related issue: #8941.
Note: The
@jsr
scope defaults to https://npm.jsr.io/ if the@jsr:registry
setting is not defined. -
Added a new setting,
dangerouslyAllowAllBuilds
, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this topnpm-workspace.yaml
:neverBuiltDependencies: []
dangerouslyAllowAllBuilds
has the same effect but also allows to be set globally via:pnpm config set dangerouslyAllowAllBuilds true
It can also be set when running a command:
pnpm install --dangerously-allow-all-builds
Patch Changes
- Fix a false negative in
verifyDepsBeforeRun
whennodeLinker
ishoisted
and there is a workspace package without dependencies andnode_modules
directory #9424. - Explicitly drop
verifyDepsBeforeRun
support fornodeLinker: pnp
. CombiningverifyDepsBeforeRun
andnodeLinker: pnp
will now print a warning.
Platinum Sponsors
|
|
|
Gold Sponsors
|
|
|
|
|
|
|
|