chore(deps): update pnpm to v10.9.0
This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| pnpm (source) | packageManager | minor | 10.8.1 -> 10.9.0 |
Release Notes
pnpm/pnpm (pnpm)
v10.9.0
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/barwill 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
@jsrscope defaults to https://npm.jsr.io/ if the@jsr:registrysetting 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: []dangerouslyAllowAllBuildshas the same effect but also allows to be set globally via:pnpm config set dangerouslyAllowAllBuilds trueIt can also be set when running a command:
pnpm install --dangerously-allow-all-builds
Patch Changes
- Fix a false negative in
verifyDepsBeforeRunwhennodeLinkerishoistedand there is a workspace package without dependencies andnode_modulesdirectory #9424. - Explicitly drop
verifyDepsBeforeRunsupport fornodeLinker: pnp. CombiningverifyDepsBeforeRunandnodeLinker: pnpwill now print a warning.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.