-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update pnpm to v9 #17
base: canary
Are you sure you want to change the base?
Conversation
528a350
to
9a8e68f
Compare
a547397
to
cac7f09
Compare
|
c16c8f9
to
e0cac04
Compare
0fcc09f
to
c8c9c7f
Compare
c8c9c7f
to
3b6a6a4
Compare
9e51783
to
0566a1a
Compare
0566a1a
to
11df785
Compare
11df785
to
0ed9f4c
Compare
0ed9f4c
to
6fc0653
Compare
6fc0653
to
6c59384
Compare
6c59384
to
b3d0f76
Compare
b3d0f76
to
844c738
Compare
71a48e8
to
9bd80e3
Compare
9bd80e3
to
7245c25
Compare
7245c25
to
85bcf6a
Compare
85bcf6a
to
44f1bce
Compare
44f1bce
to
a81619d
Compare
a81619d
to
e8e8f22
Compare
This PR contains the following updates:
8.15.9
->9.11.0
Release Notes
pnpm/pnpm (pnpm)
v9.11.0
Compare Source
v9.10.0
: pnpm 9.10Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers
, added to thelist
andwhy
commands. When--exclude-peers
is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.json
atpnpm.auditConfig.ignoreGhsas
for ignoring vulnerabilities by their GHSA code #6838.For instance:
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.9.0
Compare Source
v9.8.0
Compare Source
v9.7.1
Compare Source
v9.7.0
: pnpm 9.7Compare Source
Minor Changes
Added pnpm version management. If the
manage-package-manager-versions
setting is set totrue
, pnpm will switch to the version specified in thepackageManager
field ofpackage.json
#8363. This is the same field used by Corepack. Example:Added the ability to apply patch to all versions #8337.
If the key of
pnpm.patchedDependencies
is a package name without a version (e.g.pkg
), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version ofpkg
installed,pnpm patch pkg
and subsequentpnpm patch-commit $edit_dir
will create an entry namedpkg
inpnpm.patchedDependencies
. And pnpm will attempt to apply this patch to other versions ofpkg
in the future.Change the default edit dir location when running
pnpm patch
from a temporary directory tonode_modules/.pnpm_patches/pkg[@​version]
to allow the code editor to open the edit dir in the same file tree as the main project #8379.Substitute environment variables in config keys #6679.
Patch Changes
pnpm install
should runnode-gyp rebuild
if the project has abinding.gyp
file even if the project doesn't have an install script #8293.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.6.0
: pnpm 9.6Compare Source
Minor Changes
pnpm.executionEnv.nodeVersion
inpackage.json
) for running lifecycle scripts per each package in a workspace #6720.catalogs:
protocol #8303.Patch Changes
pnpm deploy
command now supports thecatalog:
protocol #8298.pnpm outdated
command now supports thecatalog:
protocol #8304.pnpm patch
withoutnode_modules/.modules.yaml
#8257.pnpm exec
command #7608.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.5.0
Compare Source
v9.4.0
Compare Source
v9.3.0
Compare Source
Minor Changes
peers-suffix-max-length
setting #8177.Patch Changes
reporter-hide-prefix
totrue
by default forpnpm exec
. In order to show prefix, the user now has to explicitly setreporter-hide-prefix=false
#8174.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.2.0
Compare Source
Minor Changes
package-manager-strict-version
is set totrue
, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field ofpackage.json
.Patch Changes
@yarnpkg/pnp
to the latest version, fixing issue withnode:
imports #8161.package.json
#8087.exec
now also streams prefixed output when--recursive
or--parallel
is specified just asrun
does #8065.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.4
Compare Source
v9.1.3
Compare Source
v9.1.2
Compare Source
Patch Changes
pnpm licenses
output are not misplaced anymore #8071.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
Major Changes
Node.js v16 support discontinued
If you still require Node.js 16, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the
@pnpm/exe
package.Configuration updates:
dedupe-injected-deps
: enabled by default.link-workspace-packages
: disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the workspace protocol.hoist-workspace-packages
: enabled by default.enable-pre-post-scripts
: enabled by default.~/.local/state/pnpm
).package.json
file for apackageManager
field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.Lockfile changes:
Dependency resolution changes:
Related issue: #7444.
Related PR: #7606.
pnpm licenses list
prints license information of all versions of the same package in case different versions use different licenses. The format of thepnpm licenses list --json
output has been changed #7528.A new command added for printing completion code to the console:
pnpm completion [shell]
. The old command that modified the user's shell dotfiles has been removed #3083.When installing git-hosted dependencies, only pick the files that would be packed with the package #7638.
Minor Changes
It is now possible to install only a subdirectory from a Git repository.
For example,
pnpm add github:user/repo#path:packages/foo
will add a dependency from thepackages/foo
subdirectory.This new parameter may be combined with other supported parameters separated by
&
. For instance, the next command will install the same package from thedev
branch:pnpm add github:user/repo#dev&path:packages/bar
.Related issue: #4765.
Related PR: #7487.
node-gyp
updated to version 10.PowerShell completion support added #7597.
Support
node-options
option inside.npmrc
file when running scripts #7596.Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported:
<registryURL>:certfile
,<registryURL>:keyfile
, and<registryURL>:ca
. For instance:Related issue: #7427.
Related PR: #7626.
Add a field named
ignoredOptionalDependencies
. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped #7714.The checksum of the
.pnpmfile.cjs
is saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes #7662.Added cache for
pnpm dlx
#5277.Patch Changes
--lockfile-only
installation #1328.pnpm dlx
should not read settings fromConfiguration
📅 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.