v10.13.1

Compare Source

Patch Changes

• Run user defined pnpmfiles after pnpmfiles of plugins.

v10.13.0

Compare Source

Minor Changes

• Added the possibility to load multiple pnpmfiles. Thepnpmfile setting can now accept a list of pnpmfile locations#​9702.

• pnpm will now automatically load thepnpmfile.cjs file from anyconfig dependency named@pnpm/plugin-* orpnpm-plugin-*#​9729.

  The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to thepnpmfile.cjs files in the config dependencies can be explicitly listed using thepnpmfile setting inpnpm-workspace.yaml.

Patch Changes

• When patching dependencies installed viapkg.pr.new, treat them as Git tarball URLs#​9694.
• Prevent conflicts between local projects' config and the global config indangerouslyAllowAllBuilds,onlyBuiltDependencies,onlyBuiltDependenciesFile, andneverBuiltDependencies#​9628.
• Sort keys inpnpm-workspace.yaml with deep#​9701.
• Thepnpm rebuild command should not add pkgs included inignoredBuiltDependencies toignoredBuilds innode_modules/.modules.yaml#​9338.
• Replacedshell-quote withshlex for quoting command arguments#​9381.

v10.12.4

Compare Source

Patch Changes

• Fixpnpm licenses command for local dependencies#​9583.

• Fix a bug in whichpnpm ls --filter=not-exist --json prints nothing instead of an empty array#​9672.

• Fix a deadlock that sometimes happens during peer dependency resolution#​9673.

• Runningpnpm install afterpnpm fetch should hoist all dependencies that need to be hoisted.
  Fixes a regression introduced in [v10.12.2] by [#​9648]; resolves [#​9689].

  [v10.12.2]:https://redirect.github.com/pnpm/pnpm/releases/tag/v10.12.2Add commentMore actions
  [#​9648]:https://github.com/pnpm/pnpm/pull/9648
  [#​9689]:https://github.com/pnpm/pnpm/issues/9689

v10.12.3

Compare Source

Patch Changes

• Restore hoisting of optional peer dependencies when installing with an outdated lockfile.
  Regression introduced inv10.12.2 by#​9648; resolves#​9685.

v10.12.2

Compare Source

Patch Changes

• Fixed hoisting withenableGlobalVirtualStore set totrue#​9648.
• Fix the--help and-h flags not working as expected for thepnpm create command.
• The dependency package path output by thepnpm licenses list --json command is incorrect.
• Fix a bug in whichpnpm deploy fails due to overridden dependencies having peer dependencies causingERR_PNPM_OUTDATED_LOCKFILE#​9595.

v10.12.1

Minor Changes

• Experimental. Added support for global virtual stores. When enabled,node_modules contains only symlinks to a central virtual store, rather tonode_modules/.pnpm. By default, this central store is located at<store-path>/links (you can find the store path by runningpnpm store path).

  In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

  This is conceptually similar to howNixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

  To enable the global virtual store, setenableGlobalVirtualStore: true in your rootpnpm-workspace.yaml, or globally via:

  pnpm config -gset enable-global-virtual-storetrue

  NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

  Related PR:#​8190

• Thepnpm update command now supports updatingcatalog: protocol dependencies and writes new specifiers topnpm-workspace.yaml.
• Added two new CLI options (--save-catalog and--save-catalog-name=<name>) topnpm add to save new dependencies as catalog entries.catalog: orcatalog:<name> will be added topackage.json and the package specifier will be added to thecatalogs orcatalog[<name>] object inpnpm-workspace.yaml#​9425.
• Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead#​9605.
• Added a new setting calledci for explicitly telling pnpm if the current environment is a CI or not.

Patch Changes

• Sort versions printed bypnpm patch using semantic versioning rules.
• Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects#​9598.
• Revert#​9574 to fix a regression#​9596.

v10.11.1

Compare Source

Patch Changes

• Fix an issue in whichpnpm deploy --legacy creates unexpected directories when the rootpackage.json has a workspace package as a peer dependency#​9550.
• Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#​9531)
• Installation should not exit with an error ifstrictPeerDependencies istrue but all issues are ignored bypeerDependencyRules#​9505.
• Usepnpm_config_ env variables instead ofnpm_config_#​9571.
• Fix a regression (in v10.9.0) causing the--lockfile-only flag onpnpm update to produce a differentpnpm-lock.yaml than an update without the flag.
• Letpnpm deploy work in repos withoverrides wheninject-workspace-packages=true#​9283.
• Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via#​9502.
• pnpm -r --silent run should not print out section#​9563.

v10.11.0

Compare Source

Minor Changes

• A new setting added forpnpm init to create apackage.json withtype=module, wheninit-type ismodule. Works as a flag for the init command too#​9463.

• Added support for Nushell topnpm setup#​6476.

• Added two new flags to thepnpm audit command,--ignore and--ignore-unfixable#​8474.

  Ignore all vulnerabilities that have no solution:

  > pnpm audit --ignore-unfixable

  Provide a list of CVE's to ignore those specifically, even if they have a resolution.

  > pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678

• Added support for recursively running pack in every project of a workspace#​4351.

  Now you can runpnpm -r pack to pack all packages in the workspace.

Patch Changes

• pnpm version management should work, whendangerouslyAllowAllBuilds is set totrue#​9472.
• pnpm link should work from inside a workspace#​9506.
• Set the defaultworkspaceConcurrency toMath.min(os.availableParallelism(), 4)#​9493.
• Installation should not exit with an error ifstrictPeerDependencies istrue but all issues are ignored bypeerDependencyRules#​9505.
• ReadupdateConfig frompnpm-workspace.yaml#​9500.
• Add support forrecursive pack
• Removeurl.parse usage to fix warning on Node.js 24#​9492.
• pnpm run should be able to run commands from the workspace root, ifignoreScripts is set tottrue#​4858.