You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #9702.
pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-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 the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.
Patch Changes
When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #9694.
Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies#9628.
Sort keys in pnpm-workspace.yaml with deep #9701.
The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml#9338.
Replaced shell-quote with shlex for quoting command arguments #9381.
Fix pnpm licenses command for local dependencies #9583.
Fix a bug in which pnpm ls --filter=not-exist --json prints nothing instead of an empty array #9672.
Fix a deadlock that sometimes happens during peer dependency resolution #9673.
Running pnpm install after pnpm fetch should hoist all dependencies that need to be hoisted.
Fixes a regression introduced in [v10.12.2] by [#9648]; resolves [#9689].
Restore hoisting of optional peer dependencies when installing with an outdated lockfile.
Regression introduced in v10.12.2 by #9648; resolves #9685.
Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm 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 how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.
To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:
pnpm config -g set enable-global-virtual-store true
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.
The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-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 called ci for explicitly telling pnpm if the current environment is a CI or not.
Patch Changes
Sort versions printed by pnpm patch using semantic versioning rules.
Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #9598.
Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.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 if strictPeerDependencies is true but all issues are ignored by peerDependencyRules#9505.
Use pnpm_config_ env variables instead of npm_config_#9571.
Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
Let pnpm deploy work in repos with overrides when inject-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.
A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #9463.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.10.0
->10.13.1
Release Notes
pnpm/pnpm (pnpm)
v10.13.1
Compare Source
Patch Changes
v10.13.0
Compare Source
Minor Changes
Added the possibility to load multiple pnpmfiles. The
pnpmfile
setting can now accept a list of pnpmfile locations #9702.pnpm will now automatically load the
pnpmfile.cjs
file from any config 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 the
pnpmfile.cjs
files in the config dependencies can be explicitly listed using thepnpmfile
setting inpnpm-workspace.yaml
.Patch Changes
pkg.pr.new
, treat them as Git tarball URLs #9694.dangerouslyAllowAllBuilds
,onlyBuiltDependencies
,onlyBuiltDependenciesFile
, andneverBuiltDependencies
#9628.pnpm-workspace.yaml
with deep #9701.pnpm rebuild
command should not add pkgs included inignoredBuiltDependencies
toignoredBuilds
innode_modules/.modules.yaml
#9338.shell-quote
withshlex
for quoting command arguments #9381.v10.12.4
Compare Source
Patch Changes
Fix
pnpm licenses
command for local dependencies #9583.Fix a bug in which
pnpm ls --filter=not-exist --json
prints nothing instead of an empty array #9672.Fix a deadlock that sometimes happens during peer dependency resolution #9673.
Running
pnpm 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
Regression introduced in v10.12.2 by #9648; resolves #9685.
v10.12.2
Compare Source
Patch Changes
enableGlobalVirtualStore
set totrue
#9648.--help
and-h
flags not working as expected for thepnpm create
command.pnpm licenses list --json
command is incorrect.pnpm 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.
To enable the global virtual store, set
enableGlobalVirtualStore: true
in your rootpnpm-workspace.yaml
, or globally via: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
pnpm update
command now supports updatingcatalog:
protocol dependencies and writes new specifiers topnpm-workspace.yaml
.--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.ci
for explicitly telling pnpm if the current environment is a CI or not.Patch Changes
pnpm patch
using semantic versioning rules.v10.11.1
Compare Source
Patch Changes
pnpm deploy --legacy
creates unexpected directories when the rootpackage.json
has a workspace package as a peer dependency #9550.strictPeerDependencies
istrue
but all issues are ignored bypeerDependencyRules
#9505.pnpm_config_
env variables instead ofnpm_config_
#9571.--lockfile-only
flag onpnpm update
to produce a differentpnpm-lock.yaml
than an update without the flag.pnpm deploy
work in repos withoverrides
wheninject-workspace-packages=true
#9283.pnpm -r --silent run
should not print out section #9563.v10.11.0
Compare Source
Minor Changes
A new setting added for
pnpm init
to create apackage.json
withtype=module
, wheninit-type
ismodule
. Works as a flag for the init command too #9463.Added support for Nushell to
pnpm setup
#6476.Added two new flags to the
pnpm 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 run
pnpm -r pack
to pack all packages in the workspace.Patch Changes
dangerouslyAllowAllBuilds
is set totrue
#9472.pnpm link
should work from inside a workspace #9506.workspaceConcurrency
toMath.min(os.availableParallelism(), 4)
#9493.strictPeerDependencies
istrue
but all issues are ignored bypeerDependencyRules
#9505.updateConfig
frompnpm-workspace.yaml
#9500.recursive pack
url.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.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.