chore(deps): update pnpm to v10.14.0
This MR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| pnpm (source) | 10.13.1 -> 10.14.0 |
Release Notes
pnpm/pnpm (pnpm)
v10.14.0
Minor Changes
-
Added support for JavaScript runtime resolution
Declare Node.js, Deno, or Bun in
devEngines.runtime(insidepackage.json) and let pnpm download and pin it automatically.Usage example:
{ "devEngines": { "runtime": { "name": "node", "version": "^24.4.0", "onFail": "download" (we only support the "download" value for now) } } }How it works:
-
pnpm installresolves your specified range to the latest matching runtime version. - The exact version (and checksum) is saved in the lockfile.
- Scripts use the local runtime, ensuring consistency across environments.
Why this is better:
- This new setting supports also Deno and Bun (vs. our Node-only settings
useNodeVersionandexecutionEnv.nodeVersion) - Supports version ranges (not just a fixed version).
- The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
- It can be used on any workspace project (like
executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes. - For now
devEngines.runtimesetting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.
Related MR: #9755.
-
-
Add
--cpu,--libc, and--ostopnpm install,pnpm add, andpnpm dlxto customizesupportedArchitecturesvia the CLI #7510.
Patch Changes
- Fix a bug in which
pnpm adddownloads packages whoselibcdiffer frompnpm.supportedArchitectures.libc. - The integrities of the downloaded Node.js artifacts are verified #9750.
- Allow
dlxto parse CLI flags and options between thedlxcommand and the command to run or between thedlxcommand and--#9719. -
pnpm install --prodshould removing hoisted dev dependencies #9782. - Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
- Fix a bug causing
pnpm installto incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.