v10.20.0

Compare Source

Minor Changes

• Support--all option inpnpm --help to list all commands#​8628.

Patch Changes

• When thelatest version doesn't satisfy the maturity requirement configured byminimumReleaseAge, pick the highest version that is mature enough, even if it has a different major version#​10100.
• create command should not verify patch info.
• SetmanagePackageManagerVersions tofalse, when switching to a different version of pnpm CLI, in order to avoid subsequent switches#​10063.

v10.19.0

Compare Source

Minor Changes

• You can now allow specific versions of dependencies to run postinstall scripts.onlyBuiltDependencies now accepts package names with lists of trusted versions. For example:

  onlyBuiltDependencies:  -nx@21.6.4 || 21.6.5  -esbuild@0.25.1

  Related PR:#​10104.

• Added support for exact versions inminimumReleaseAgeExclude#​9985.

  You can now list one or more specific versions that pnpm should allow to install, even if those versions don’t satisfy the maturity requirement set byminimumReleaseAge. For example:

  minimumReleaseAge:1440minimumReleaseAgeExclude:  -nx@21.6.5  -webpack@4.47.0 || 5.102.1

v10.18.3

Compare Source

Patch Changes

• Fix a bug where pnpm would infinitely recurse when usingverifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts#​10060.
• Fixed scoped registry keys (e.g.,@scope:registry) being parsed as property paths inpnpm config get when--location=project is used#​9362.
• Remove pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings#​9646.
• Fixed EISDIR error when bin field points to a directory#​9441.
• Preserve version and hasBin for variations packages#​10022.
• Fixedpnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings)#​9884.
• When bothpnpm-workspace.yaml and.npmrc exist,pnpm config set --location=project now writes topnpm-workspace.yaml (matching read priority)#​10072.
• Prevent a table width error inpnpm outdated --long#​10040.
• Sync bin links after injected dependencies are updated by build scripts. This ensures that binaries created during build processes are properly linked and accessible to consuming projects#​10057.

v10.18.2

Compare Source

Patch Changes

• pnpm outdated --long should work#​10040.
• Replace ndjson with split2. Reduce the bundle size of pnpm CLI#​10054.
• pnpm dlx should request the full metadata of packages, whenminimumReleaseAge is set#​9963.
• pnpm version switching should work when the pnpm home directory is in a symlinked directory#​9715.
• FixEPIPE errors when piping output to other commands#​10027.

v10.18.1

Compare Source

Patch Changes

• Don't print a warning, when--lockfile-only is used#​8320.
• pnpm setup creates a command shim to the pnpm executable. This is needed to be able to runpnpm self-update on Windows#​5700.
• When using pnpm catalogs and running a normalpnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when usingpnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes

• Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

  Added configuration options for warning thresholds:fetchWarnTimeoutMs andfetchMinSpeedKiBps.
  Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

  Related PR:#​10025.

Patch Changes

• Retry filesystem operations on EAGAIN errors#​9959.
• Outdated command respectsminimumReleaseAge configuration#​10030.
• Correctly apply thecleanupUnusedCatalogs configuration when removing dependent packages.
• Don't fail with a meaningless error whenscriptShell is set tofalse#​8748.
• pnpm dlx should not fail whenminimumReleaseAge is set#​10037.

v10.17.1

Compare Source

Patch Changes

• When a version specifier cannot be resolved because the versions don't satisfy theminimumReleaseAge setting, print this information out in the error message#​9974.
• Fixstate.json creation path when executingpnpm patch in a workspace project#​9733.
• WhenminimumReleaseAge is set and thelatest tag is not mature enough, prefer a non-deprecated version as the newlatest#​9987.

v10.17.0

Compare Source

Minor Changes

• TheminimumReleaseAgeExclude setting now supports patterns. For instance:

  minimumReleaseAge:1440minimumReleaseAgeExclude:  -"@​eslint/*"

  Related PR:#​9984.

Patch Changes

• Don't ignore theminimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache#​9978.
• WhenminimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one#​9979.

v10.16.1

Compare Source

Patch Changes

• The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result#​9963.
• Forcibly disable ANSI color codes when generating patch diff#​9914.

v10.16.0

Compare Source

Minor Changes

• There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

  The new setting is calledminimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, settingminimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

  If you setminimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under theminimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

  minimumReleaseAgeExclude:  -webpack

  Related issue:#​9921.

• Added support forfinders#​9946.

  In the past,pnpm list andpnpm why could only search for dependencies byname (and optionally version). For example:

  pnpm why minimist

  prints the chain of dependencies to any installed instance ofminimist:

  verdaccio 5.20.1├─┬ handlebars 4.7.7│ └── minimist 1.2.8└─┬ mv 2.1.1  └─┬ mkdirp 0.5.6    └── minimist 1.2.8

  What if we want to search byother properties of a dependency, not just its name? For instance, find all packages that havereact@17 in their peer dependencies?

  This is now possible with "finder functions". Finder functions can be declared in.pnpmfile.cjs and invoked with the--find-by=<function name> flag when runningpnpm list orpnpm why.

  Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our.pnpmfile.cjs:

  module.exports={finders:{react17:(ctx)=>{returnctx.readManifest().peerDependencies?.react==="^17.0.0";},},};

  Now we can use this finder function by running:

  pnpm why --find-by=react17

  pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

  @​apollo/client 4.0.4├── @​graphql-typed-document-node/core 3.2.0└── graphql-tag 2.12.6

  It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

  module.exports={finders:{react17:(ctx)=>{constmanifest=ctx.readManifest();if(manifest.peerDependencies?.react==="^17.0.0"){return`license:${manifest.license}`;}returnfalse;},},};

  Every matched package will also print out the license from itspackage.json:

  @​apollo/client 4.0.4├── @​graphql-typed-document-node/core 3.2.0│   license: MIT└── graphql-tag 2.12.6    license: MIT

Patch Changes

• Fix deprecation warning printed when executing pnpm with Node.js 24#​9529.
• Throw an error ifnodeVersion is not set to an exact semver version#​9934.
• pnpm publish should be able to publish a.tar.gz file#​9927.
• Canceling a running process with Ctrl-C should makepnpm run return a non-zero exit code#​9626.

v10.15.1

Compare Source

Patch Changes

• Fix.pnp.cjs crash when importing subpath#​9904.
• When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies#​9913.

v10.15.0

Compare Source

Minor Changes

• Added thecleanupUnusedCatalogs configuration. When set totrue, pnpm will remove unused catalog entries during installation#​9793.
• Automatically load pnpmfiles from config dependencies that are named@*/pnpm-plugin-*#​9780.
• pnpm config get now prints an INI string for an object value#​9797.
• pnpm config get now accepts property paths (e.g.pnpm config get catalog.react,pnpm config get .catalog.react,pnpm config get 'packageExtensions["@​babel/parser"].peerDependencies["@​babel/types"]'), andpnpm config set now accepts dot-leading or subscripted keys (e.g.pnpm config set .ignoreScripts true).
• pnpm config get --json now prints a JSON serialization of config value, andpnpm config set --json now parses the input value as JSON.

Patch Changes

• Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package#​9835.
• When executing thepnpm create command, must verify whether the node version is supported even if a cache already exists#​9775.
• When making requests for the non-abbreviated packument, add*/* to theAccept header to avoid getting a 406 error on AWS CodeArtifact#​9862.
• The standalone exe version of pnpm works with glibc 2.26 again#​9734.
• Fix a regression in whichpnpm dlx pkg --help doesn't pass--help topkg#​9823.