npm · #3866 most downloaded on npm

@pnpm/exe

12.8.2pnpm/pnpm ↗New releases in your daily digest, changelog included.

Fast, disk space efficient package manager

Last release today
30 Sep 2026
Ships on a steady schedule
a new release about every 8 days
Most releases are documented
notes for 47 of the last 60 stable releases
25 versions withdrawn
withdrawn after publishing
5 years old
594 releases · first in 2021

Release timeline

594 releases since 2021

202120222023202420252026

20212026

One column per quarter.

Releases

10.26.223 Dec 2025
Improve error message when a package version exists but does not meet the minimumReleaseAge constraint. The error now clearly states that the version
Patch Changes

Improve error message when a package version exists but does not meet the minimumReleaseAge constraint. The error now clearly states that the version exists and shows a human-readable time since release (e.g., "released 6 hours ago") #10307.

Fix installation of Git dependencies using annotated tags #10335.

Previously, pnpm would store the annotated tag object's SHA in the lockfile instead of the actual commit SHA. This caused ERR_PNPM_GIT_CHECKOUT_FAILED errors because the checked-out commit hash didn't match the stored tag object hash.

Binaries of runtime engines (Node.js, Deno, Bun) are written to node_modules/.bin before lifecycle scripts (install, postinstall, prepare) are executed #10244.

Try to avoid making network calls with preferOffline #10334.

Platinum Sponsors

<table> <tbody> <tr> <td align="center" valign="middle"> <a href="https://bit.dev/?utm_source=pnpm&utm_medium=release_notes" target="_blank"><img src="https://pnpm.io/img/users/bit.svg" width="80" alt="Bit"></a> </td> </tr> </tbody> </table>

Gold Sponsors

<table> <tbody> <tr> <td align="center" valign="middle"> <a href="https://discord.com/?utm_source=pnpm&utm_medium=release_notes" target="_blank"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/discord.svg" /> <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/discord_light.svg" /> <img src="https://pnpm.io/img/users/discord.svg" width="220" alt="Discord" /> </picture> </a> </td> <td align="center" valign="middle"> <a href="https://coderabbit.ai/?utm_source=pnpm&utm_medium=release_notes" target="_blank"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/coderabbit.svg" /> <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/coderabbit_light.svg" /> <img src="https://pnpm.io/img/users/coderabbit.svg" width="220" alt="CodeRabbit" /> </picture> </a> </td> <td align="center" valign="middle"> <a href="https://workleap.com/?utm_source=pnpm&utm_medium=release_notes" target="_blank"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/workleap.svg" /> <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/workleap_light.svg" /> <img src="https://pnpm.io/img/users/workleap.svg" width="190" alt="Workleap" /> </picture> </a> </td> </tr> <tr> <td align="center" valign="middle"> <a href="https://stackblitz.com/?utm_source=pnpm&utm_medium=release_notes" target="_blank"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/stackblitz.svg" /> <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/stackblitz_light.svg" /> <img src="https://pnpm.io/img/users/stackblitz.svg" width="190" alt="Stackblitz" /> </picture> </a> </td> <td align="center" valign="middle"> <a href="https://vite.dev/?utm_source=pnpm&utm_medium=release_notes" target="_blank"> <img src="https://pnpm.io/img/users/vitejs.svg" width="42" alt="Vite"> </a> </td> </tr> </tbody> </table>

10.26.119 Dec 2025

Don't fail on pnpm add, when blockExoticSubdeps is set to true #10324.

Patch Changes

Don't fail on pnpm add, when blockExoticSubdeps is set to true #10324.
Always resolve git references to full commits and ensure HEAD points to the commit after checkout #10310.

Platinum Sponsors

Gold Sponsors

Open source →

10.26.015 Dec 2025Security

…verification and scanning for malware and vulnerabilities.

Minor Changes

Semi-breaking. Block git-hosted dependencies from running prepare scripts unless explicitly allowed in onlyBuiltDependencies #10288.
Semi-breaking. Compute integrity hash for HTTP tarball dependencies when fetching, storing it in the lockfile to prevent servers from serving altered content on subsequent installs #10287.
Added a new setting blockExoticSubdeps that prevents the resolution of exotic protocols in transitive dependencies.

When set to true, direct dependencies (those listed in your root package.json) may still use exotic sources, but all transitive dependencies must be resolved from a trusted source. Trusted sources include the configured registry, local file paths, workspace links, trusted GitHub repositories (node, bun, deno), and custom resolvers.

This helps to secure the dependency supply chain. Packages from trusted sources are considered safer, as they are typically subject to more reliable verification and scanning for malware and vulnerabilities.

Exotic sources are dependency locations that bypass the usual trusted resolution process. These protocols are specifically targeted and blocked: Git repositories (git+ssh://...) and direct URL links to tarballs (https://.../package.tgz).

Related PR: #10265.
Added support for allowBuilds, which is a new field that can be used instead of onlyBuiltDependencies and ignoredBuiltDependencies. The new allowBuilds field in your pnpm-workspace.yaml uses a map of package matchers to explicitly allow (true) or disallow (false) script execution. This allows for a single, easy-to-manage source of truth for your build permissions.

Example Usage. To explicitly allow all versions of esbuild to run scripts and prevent core-js from running them:
```
allowBuilds:
  esbuild: true
  core-js: false
```
The example above achieves the same result as the previous configuration:
```
onlyBuiltDependencies:
  - esbuild
ignoredBuiltDependencies:
  - core-js
```
Related PR: #10311
Added support for --dry-run to the pack command #10301.

Patch Changes

Show deprecation in table/list formats when latest version is deprecated #8658.
Remove the injectWorkspacePackages setting from the lockfile on the deploy command #10294.
Normalize the tarball URLs before saving them to the lockfile. URLs should not contain default ports, like :80 for http and :443 for https #10273.
When a dependency is installed via a direct URL that redirects to another URL and is immutable, the original URL is normalized and saved to package.json #10197.

Platinum Sponsors

Gold Sponsors

Open source →

10.25.08 Dec 2025

Allow loading certificates from cert, ca, and key for specific registry URLs. E.g., //registry.example.com/:ca=-----BEGIN CERTIFICATE-----.... Previou

Minor Changes

Allow loading certificates from cert, ca, and key for specific registry URLs. E.g., //registry.example.com/:ca=-----BEGIN CERTIFICATE-----.... Previously this was only working via certfile, cafile, and keyfile.

These properties are supported in .npmrc, but were ignored by pnpm, this will make pnpm read and use them as well.

Related PR: #10230.
Added a new flag called --bare to pnpm init for creating a package.json with the bare minimum of required fields #10226.

Patch Changes

Improved reporting of ignored dependency scripts #10276.
pnpm install should build any dependencies that were added to onlyBuiltDependencies and were not built yet #10256.
pnpm publish -r --force should allow to run publish over already existing versions in the registry #10272.
Don't fail with a ERR_PNPM_MISSING_TIME error if a package that is excluded from trust policy checks is missing the time field in the metadata.

Platinum Sponsors

Gold Sponsors

Open source →

10.24.027 Nov 2025

Increased network concurrency on machines with many CPU cores. pnpm now automatically selects a network concurrency between 16 and 64, based on the nu

Minor Changes

Increased network concurrency on machines with many CPU cores. pnpm now automatically selects a network concurrency between 16 and 64, based on the number of pnpm workers (calculated as workers × 3). This improves performance on high-core systems #10068.

Patch Changes

trustPolicy should ignore the trust evidences of prerelease versions, when installing a non-prerelease version.
Handle ENOENT errors thrown by fs.linkSync(), which can occur in containerized environments (OverlayFS) instead of EXDEV. The operation now gracefully falls back to fs.copyFileSync() in these cases #10217.
Reverted: pnpm self-update should download pnpm from the configured npm registry #10205.
Packages that don't have a package.json file (like Node.js) should not be reimported from the store on every install. Another file from the package should be checked in order to verify its presence in node_modules.
Correctly read auth tokens for URLs that contain underscores #17.

Platinum Sponsors

Gold Sponsors

Open source →

10.23.020 Nov 2025

Added --lockfile-only option to pnpm list #10020.

Minor Changes

Added --lockfile-only option to pnpm list #10020.

Patch Changes

pnpm self-update should download pnpm from the configured npm registry #10205.
pnpm self-update should always install the non-executable pnpm package (pnpm in the registry) and never the @pnpm/exe package, when installing v11 or newer. We currently cannot ship @pnpm/exe as pkg doesn't work with ESM #10190.
Node.js runtime is not added to "dependencies" on pnpm add, if there's a engines.runtime setting declared in package.json #10209.
The installation should fail if an optional dependency cannot be installed due to a trust policy check failure #10208.
pnpm list and pnpm why now display npm: protocol for aliased packages (e.g., foo npm:is-odd@3.0.1) #8660.
Don't add an extra slash to the Node.js mirror URL #10204.
pnpm store prune should not fail if the store contains Node.js packages #10131.

Platinum Sponsors

Gold Sponsors

Open source →

10.22.012 Nov 2025

Added support for trustPolicyExclude #10164.

Minor Changes

Added support for trustPolicyExclude #10164.

You can now list one or more specific packages or versions that pnpm should allow to install, even if those packages don't satisfy the trust policy requirement. For example:
```
trustPolicy: no-downgrade
trustPolicyExclude:
  - chokidar@4.0.3
  - webpack@4.47.0 || 5.102.1
```
Allow to override the engines field on publish by the publishConfig.engines field.

Patch Changes

Don't crash when two processes of pnpm are hardlinking the contents of a directory to the same destination simultaneously #10179.

Platinum Sponsors

Gold Sponsors

Open source →

10.21.09 Nov 2025

Node.js Runtime Installation for Dependencies. Added support for automatic Node.js runtime installation for dependencies. pnpm will now install the No

Minor Changes

Node.js Runtime Installation for Dependencies. Added support for automatic Node.js runtime installation for dependencies. pnpm will now install the Node.js version required by a dependency if that dependency declares a Node.js runtime in the "engines" field. For example:
```
{
  "engines": {
    "runtime": {
      "name": "node",
      "version": "^24.11.0",
      "onFail": "download"
    }
  }
}
```
If the package with the Node.js runtime dependency is a CLI app, pnpm will bind the CLI app to the required Node.js version. This ensures that, regardless of the globally installed Node.js instance, the CLI will use the compatible version of Node.js.

If the package has a postinstall script, that script will be executed using the specified Node.js version.

Related PR: #10141
Added a new setting: trustPolicy.

When set to no-downgrade, pnpm will fail installation if a package’s trust level has decreased compared to previous releases — for example, if it was previously published by a trusted publisher but now only has provenance or no trust evidence. This helps prevent installing potentially compromised versions of a package.

Related issue: #8889.
Added support for pnpm config get globalconfig to retrieve the global config file path #9977.

Patch Changes

When a user runs pnpm update on a dependency that is not directly listed in package.json, none of the direct dependencies should be updated #10155.
Don't crash when two processes of pnpm are hardlinking the contents of a directory to the same destination simultaneously #10160.
Setting gitBranchLockfile and related settings via pnpm-workspace.yaml should work #9651.

Platinum Sponsors

Gold Sponsors

Open source →

10.20.028 Oct 2025

Support --all option in pnpm --help to list all commands #8628.

Minor Changes

Support --all option in pnpm --help to list all commands #8628.

Patch Changes

When the latest version doesn't satisfy the maturity requirement configured by minimumReleaseAge, pick the highest version that is mature enough, even if it has a different major version #10100.
create command should not verify patch info.
Set managePackageManagerVersions to false, when switching to a different version of pnpm CLI, in order to avoid subsequent switches #10063.

Platinum Sponsors

Gold Sponsors

Open source →

10.19.021 Oct 2025

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

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 in minimumReleaseAgeExclude #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 by minimumReleaseAge. For example:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - nx@21.6.5
  - webpack@4.47.0 || 5.102.1
```

Platinum Sponsors

Gold Sponsors

Open source →

10.18.314 Oct 2025

Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts

Patch Changes

Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: 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 in pnpm 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.
Fixed pnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings) #9884.
When both pnpm-workspace.yaml and .npmrc exist, pnpm config set --location=project now writes to pnpm-workspace.yaml (matching read priority) #10072.
Prevent a table width error in pnpm 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.

Platinum Sponsors

Gold Sponsors

Open source →

10.18.29 Oct 2025

pnpm outdated --long should work #10040.

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, when minimumReleaseAge is set #9963.
pnpm version switching should work when the pnpm home directory is in a symlinked directory #9715.
Fix EPIPE errors when piping output to other commands #10027.

Platinum Sponsors

Gold Sponsors

Open source →

10.18.16 Oct 2025

Don't print a warning, when --lockfile-only is used #8320.

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 run pnpm self-update on Windows #5700.
When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

Platinum Sponsors

Gold Sponsors

Open source →

10.18.02 Oct 2025

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

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 and fetchMinSpeedKiBps. 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 respects minimumReleaseAge configuration #10030.
Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
Don't fail with a meaningless error when scriptShell is set to false #8748.
pnpm dlx should not fail when minimumReleaseAge is set #10037.

Platinum Sponsors

Gold Sponsors

Open source →

10.17.122 Sept 2025Deprecated

When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #9987.

Patch Changes

When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #9974.
Fix state.json creation path when executing pnpm patch in a workspace project #9733.
When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #9987.

Platinum Sponsors

Gold Sponsors

Open source →

10.17.017 Sept 2025

The minimumReleaseAgeExclude setting now supports patterns. For instance:

Minor Changes

The minimumReleaseAgeExclude setting now supports patterns. For instance:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@eslint/*"
```
Related PR: #9984.

Patch Changes

Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
When minimumReleaseAge 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.

Platinum Sponsors

Gold Sponsors

Open source →

10.16.113 Sept 2025

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

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.

Platinum Sponsors

Gold Sponsors

Open source →

10.16.012 Sept 2025Deprecated

Fix deprecation warning printed when executing pnpm with Node.js 24 #9529.

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 called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude 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 for finders #9946.

In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:
```
pnpm why minimist
```
prints the chain of dependencies to any installed instance of minimist:
```
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 by other properties of a dependency, not just its name? For instance, find all packages that have react@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 running pnpm list or pnpm 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) => {
      return ctx.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) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};
```
Every matched package will also print out the license from its package.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 if nodeVersion 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 make pnpm run return a non-zero exit code #9626.

Platinum Sponsors

Gold Sponsors

Open source →

10.15.11 Sept 2025

Fix .pnp.cjs crash when importing subpath #9904.

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.

Platinum Sponsors

Gold Sponsors

Open source →

10.15.019 Aug 2025

Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #9793.

Minor Changes

Added the cleanupUnusedCatalogs configuration. When set to true, 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"]'), and pnpm 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, and pnpm 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 the pnpm 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 the Accept 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 which pnpm dlx pkg --help doesn't pass --help to pkg #9823.

Platinum Sponsors

Gold Sponsors

Open source →

10.14.031 Jul 2025

Added support for JavaScript runtime installation

Minor Changes

Added support for JavaScript runtime installation

Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.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:
1. pnpm install resolves your specified range to the latest matching runtime version.
2. The exact version (and checksum) is saved in the lockfile.
3. Scripts use the local runtime, ensuring consistency across environments.
Why this is better:
1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
2. Supports version ranges (not just a fixed version).
3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.
Related PR: #9755.
Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #7510.

Patch Changes

Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
The integrities of the downloaded Node.js artifacts are verified #9750.
Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #9719.
pnpm install --prod should 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 install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

Platinum Sponsors

Gold Sponsors

Open source →

10.13.19 Jul 2025

Run user defined pnpmfiles after pnpmfiles of plugins.

Patch Changes

Run user defined pnpmfiles after pnpmfiles of plugins.

Platinum Sponsors

Gold Sponsors

Open source →

10.13.09 Jul 2025

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

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-* 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.

Platinum Sponsors

Gold Sponsors

Open source →

10.12.426 Jun 2025

Fix pnpm licenses command for local dependencies #9583.

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 after pnpm fetch should hoist all dependencies that need to be hoisted. Fixes a regression introduced in v10.12.2 by #9648; resolves #9689.

Platinum Sponsors

Gold Sponsors

Open source →

10.12.324 Jun 2025

Restore hoisting of optional peer dependencies when installing with an outdated lockfile. Regression introduced in [v10.12.2] by [#9648]; resolves [#9

Patch Changes

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

Platinum Sponsors

Gold Sponsors

Open source →

10.12.223 Jun 2025

Fixed hoisting with enableGlobalVirtualStore set to true #9648.

Patch Changes

Fixed hoisting with enableGlobalVirtualStore set to true #9648.
Fix the --help and -h flags not working as expected for the pnpm create command.
The dependency package path output by the pnpm licenses list --json command is incorrect.
Fix a bug in which pnpm deploy fails due to overridden dependencies having peer dependencies causing ERR_PNPM_OUTDATED_LOCKFILE #9595.

Platinum Sponsors

Gold Sponsors

Open source →

10.12.18 Jun 2025

Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather than to no

Minor Changes

Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather than 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.

Short demo of the speed of installation with this new setting enabled: https://www.youtube.com/watch?v=pNDFfJvaubY&ab_channel=pnpm

Related PR: #8190

The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
A new catalogMode setting is available for controlling if and how dependencies are added to the default catalog. It can be configured to several modes:
- strict: Only allows dependency versions from the catalog. Adding a dependency outside the catalog's version range will cause an error.
- prefer: Prefers catalog versions, but will fall back to direct dependencies if no compatible version is found.
- manual (default): Does not automatically add dependencies to the catalog.
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.
Revert #9574 to fix a regression #9596.

Platinum Sponsors

Gold Sponsors

Open source →

10.11.12 Jun 2025

Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #955

Patch Changes

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.

Platinum Sponsors

Gold Sponsors

Open source →

10.11.013 May 2025Security

Ignore all vulnerabilities that have no solution:

Minor Changes

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.
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

pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #9472.
pnpm link should work from inside a workspace #9506.
Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #9493.
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Read updateConfig from pnpm-workspace.yaml #9500.
Add support for recursive pack
Remove url.parse usage to fix warning on Node.js 24 #9492.
pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #4858.

Platinum Sponsors

Gold Sponsors

Open source →

10.10.027 Apr 2025

Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.

Minor Changes

Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.

Patch Changes

Fix cd command, when shellEmulator is true #7838.
Sort keys in pnpm-workspace.yaml #9453.
Pass the npm_package_json environment variable to the executed scripts #9452.
Fixed a mistake in the description of the --reporter=silent option.

Platinum Sponsors

Gold Sponsors

Open source →

10.9.021 Apr 2025

Added support for installing JSR packages. You can now install JSR packages using the following syntax:

Minor Changes

Added support for installing JSR packages. You can now install JSR packages using the following syntax:
```
pnpm add jsr:<pkg_name>
```
or with a version range:
```
pnpm add jsr:<pkg_name>@<range>
```
For example, running:
```
pnpm add jsr:@foo/bar
```
will add the following entry to your package.json:
```
{
  "dependencies": {
    "@foo/bar": "jsr:^0.1.2"
  }
}
```
When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
```
{
  "dependencies": {
    "@foo/bar": "npm:@jsr/foo__bar@^0.1.2"
  }
}
```
Related issue: #8941.

Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.
Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:
```
neverBuiltDependencies: []
```
dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:
```
pnpm config set dangerouslyAllowAllBuilds true
```
It can also be set when running a command:
```
pnpm install --dangerously-allow-all-builds
```

Patch Changes

Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #9424.
Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

Platinum Sponsors

Gold Sponsors

Open source →

10.8.114 Apr 2025

Removed bright white highlighting, which didn't look good on some light themes #9389.

Patch Changes

Removed bright white highlighting, which didn't look good on some light themes #9389.
If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #9404.
The patch file path saved by the pnpm patch-commit and patch-remove commands should be a relative path #9403.

Platinum Sponsors

Gold Sponsors

Open source →

10.8.07 Apr 2025

Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

Minor Changes

Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:
```
module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};
```
Now you can use the pnpm add command with the --config flag to install new configurational dependencies #9377.

Patch Changes

Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #9169.
pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #9365.

Platinum Sponsors

Gold Sponsors

Open source →

10.7.11 Apr 2025

pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #9355.

Patch Changes

pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #9355.
pnpm config get should read auth related settings via npm CLI #9345.
Replace leading ~/ in a path in .npmrc with the home directory #9217.

Platinum Sponsors

Gold Sponsors

Open source →

10.7.026 Mar 2025Deprecated

Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  foo@2.1.0: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to foo@2.1.0, patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING] The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  'foo@2.2.0-2.8.0': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.519 Mar 2025

Remove warnings after having explicitly approved no builds #9296.

Patch Changes

Remove warnings after having explicitly approved no builds #9296.
When installing different dependency packages, should retain the ignoredBuilds field in the .modules.yaml file #9240.
Fix usages of the catalog: protocol in injected local workspace packages. This previously errored with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER. #8715
Setting workspace-concurrency to less than or equal to 0 should work #9297.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.417 Mar 2025

Fix pnpm dlx with --allow-build flag #9263.

Patch Changes

Fix pnpm dlx with --allow-build flag #9263.
Invalid Node.js version in use-node-version should not cause pnpm itself to break #9276.
The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.313 Mar 2025

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #92

Patch Changes

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #9211.
Add the missing node-options config to recursive run #9180.
Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

See details in #9259.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.210 Mar 2025

pnpm self-update should always update the version in the packageManager field of package.json.

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.
pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
Don't show info output when --loglevel=error is used.
peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.17 Mar 2025

The pnpm CLI process should not stay hanging, when --silent reporting is used.

Patch Changes

The pnpm CLI process should not stay hanging, when --silent reporting is used.
When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
Don't ignore pnpm.patchedDependencies from package.json #9226.
When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

Platinum Sponsors

Gold Sponsors

Open source →

10.6.06 Mar 2025

pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #9211.

Minor Changes

pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #9211.

pnpm-workspace.yaml example:
```
verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@types/react"
```
Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes

pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #9169.
pnpm deploy should not remove fields from the deployed package's package.json file #9215.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
Fix pnpm deploy creating a package.json without the imports and license field #9193.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112

Platinum Sponsors

Gold Sponsors

Open source →

10.5.227 Feb 2025

The pnpm config set command should change the global .npmrc file by default. This was a regression introduced by #9151 and shipped in pnpm v10.5.0.

Patch Changes

The pnpm config set command should change the global .npmrc file by default. This was a regression introduced by #9151 and shipped in pnpm v10.5.0.

Platinum Sponsors

Gold Sponsors

Open source →

10.5.126 Feb 2025

Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #9170.

Patch Changes

Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #9170.
Fix the update of pnpm-workspace.yaml by the pnpm approve-builds command #9168.
Normalize generated link paths in package.json #9163
Specifying overrides in pnpm-workspace.yaml should work.
pnpm dlx should ignore settings from the package.json file in the current working directory #9178.

Platinum Sponsors

Gold Sponsors

Open source →

10.5.025 Feb 2025

The pnpm.* settings from package.json can now be specified in the pnpm-workspace.yaml file instead #9121.

Minor Changes

The pnpm.* settings from package.json can now be specified in the pnpm-workspace.yaml file instead #9121.

package.json:
```
{
  "pnpm": {
    "onlyBuiltDependencies": ["esbuild", "fuse-native"]
  }
}
```
pnpm-workspace.yaml:
```
onlyBuiltDependencies:
- esbuild
- fuse-native
```
Added support for automatically syncing files of injected workspace packages after pnpm run #9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:
```
sync-injected-deps-after-scripts[]=compile
```
The packages field in pnpm-workspace.yaml became optional.

Patch Changes

pnpm link with no parameters should work as if --global is specified #9151.
Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
pnpm link <path> should calculate relative path from the root of the workspace directory #9132.
Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

Platinum Sponsors

Gold Sponsors

Open source →

10.4.116 Feb 2025

Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #9105.

Patch Changes

Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #9105.
Print pnpm's version after the execution time at the end of the console output.
Print warning about ignored builds of dependencies on repeat install #9106.
Setting init-package-manager should work.

Platinum Sponsors

Gold Sponsors

Open source →

10.3.010 Feb 2025

Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed b

See breaking changes in v10

Minor Changes

Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #9071.

Patch Changes

Fix a false negative of verify-deps-before-run after pnpm install --production|--no-optional #9019.
Print the warning about blocked installation scripts at the end of the installation output and make it more prominent.

Platinum Sponsors

Gold Sponsors

Open source →

10.2.16 Feb 2025

Don't read a package from side-effects cache if it isn't allowed to be built #9042.

Patch Changes

Don't read a package from side-effects cache if it isn't allowed to be built #9042.
pnpm approve-builds should work, when executed from a subdirectory of a workspace #9042.
pnpm deploy --legacy should work without injected dependencies.
Add information about how to deploy without "injected dependencies" to the "pnpm deploy" error message.

Platinum Sponsors

Gold Sponsors

Open source →

10.2.03 Feb 2025

Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

See breaking changes in v10

Minor Changes

Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:
```
pnpm --allow-build=esbuild dlx bundle
```
Related PR: #9026.

Patch Changes

Quote args for scripts with shell-quote to support new lines (on POSIX only) #8980.
Fix a bug in which pnpm deploy fails to read the correct projectId when the deploy source is the same as the workspace directory #9001.
Proxy settings should be respected, when resolving Git-hosted dependencies #6530.
Prevent overrides from adding invalid version ranges to peerDependencies by keeping the peerDependencies and overriding them with prod dependencies #8978.
Sort the package names in the "pnpm.onlyBuiltDependencies" list saved by pnpm approve-builds.

Platinum Sponsors

Gold Sponsors

Open source →

10.1.026 Jan 2025

Added a new command for printing the list of dependencies with ignored build scripts: pnpm ignored-builds #8963.

See breaking changes in v10

Minor Changes

Added a new command for printing the list of dependencies with ignored build scripts: pnpm ignored-builds #8963.
Added a new command for approving dependencies for running scripts during installation: pnpm approve-builds #8963.
Added a new setting called optimistic-repeat-install. When enabled, a fast check will be performed before proceeding to installation. This way a repeat install or an install on a project with everything up-to-date becomes a lot faster. But some edge cases might arise, so we keep it disabled by default for now #8977.
Added a new field "pnpm.ignoredBuiltDependencies" for explicitly listing packages that should not be built. When a package is in the list, pnpm will not print an info message about that package not being built #8935.

Patch Changes

Verify that the package name is valid when executing the publish command.
When running pnpm install, the preprepare and postprepare scripts of the project should be executed #8989.
Allow workspace: and catalog: to be part of wider version range in peerDependencies.
pnpm deploy should inherit the pnpm object from the root package.json #8991.
Make sure that the deletion of a node_modules in a sub-project of a monorepo is detected as out-of-date #8959.
Fix infinite loop caused by lifecycle scripts using pnpm to execute other scripts during pnpm install with verify-deps-before-run=install #8954.
Replace strip-ansi with the built-in util.stripVTControlCharacters #9009.
Do not print patched dependencies as ignored dependencies that require a build #8952.

Platinum Sponsors

Gold Sponsors

Open source →

10.0.07 Jan 2025Breaking

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to…

Major Changes

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the pnpm.onlyBuiltDependencies field of package.json #8897. For example:
```
{
  "pnpm": {
    "onlyBuiltDependencies": ["fsevents"]
  }
}
```
Read pnpm 10.0.0 Blocks Lifecycle Scripts by Default to learn about the motivation of the change.

If you want the old pre v10 behaviour, so you want to allow all dependencies to run postinstall scripts, then add this to your package.json:
```
{
  "pnpm": {
    "neverBuiltDependencies": []
  }
}
```
pnpm link behavior updated:

The pnpm link command now adds overrides to the root package.json.
- In a workspace: The override is added to the root of the workspace, linking the dependency to all projects in the workspace.
- Global linking: To link a package globally, run pnpm link from the package’s directory. Previously, you needed to use pnpm link -g. Related PR: #8653
Secure hashing with SHA256:

Various hashing algorithms have been updated to SHA256 for enhanced security and consistency:
- Long paths inside node_modules/.pnpm are now hashed with SHA256.
- Long peer dependency hashes in the lockfile now use SHA256 instead of MD5. (This affects very few users since these are only used for long keys.)
- The hash stored in the packageExtensionsChecksum field of pnpm-lock.yaml is now SHA256.
- The side effects cache keys now use SHA256.
- The pnpmfile checksum in the lockfile now uses SHA256 (#8530).
- The patch file checksums in the lockfile now use SHA256.
Configuration updates:
- manage-package-manager-versions: enabled by default. pnpm now manages its own version based on the packageManager field in package.json by default.
- public-hoist-pattern: nothing is hoisted by default. Packages containing eslint or prettier in their name are no longer hoisted to the root of node_modules. Related Issue: #8378
- Upgraded @yarnpkg/extensions to v2.0.3. This may alter your lockfile.
- virtual-store-dir-max-length: the default value on Windows has been reduced to 60 characters.
- Reduced environment variables for scripts: During script execution, fewer npm_package_* environment variables are set. Only name, version, bin, engines, and config remain. Related Issue: #8552
- All dependencies are now installed even if NODE_ENV=production. Related Issue: #8827
Changes to the global store:
- Store version bumped to v10.
- Some registries allow identical content to be published under different package names or versions. To accommodate this, index files in the store are now stored using both the content hash and package identifier.
  
  This approach ensures that we can:
  1. Validate that the integrity in the lockfile corresponds to the correct package, which might not be the case after a poorly resolved Git conflict.
  2. Allow the same content to be referenced by different packages or different versions of the same package. Related PR: #8510 Related Issue: #8204
- More efficient side effects indexing. The structure of index files in the store has changed. Side effects are now tracked more efficiently by listing only file differences rather than all files. Related PR: #8636
- A new index directory stores package content mappings. Previously, these files were in files.
Other breaking changes:
- The # character is now escaped in directory names within node_modules/.pnpm. Related PR: #8557
- Running pnpm add --global pnpm or pnpm add --global @pnpm/exe now fails with an error message, directing you to use pnpm self-update instead. Related PR: #8728
- Dependencies added via a URL now record the final resolved URL in the lockfile, ensuring that any redirects are fully captured. Related Issue: #8833
- The pnpm deploy command now only works in workspaces that have inject-workspace-packages=true. This limitation is introduced to allow us to create a proper lockfile for the deployed project using the workspace lockfile.
- Removed conversion from lockfile v6 to v9. If you need v6-to-v9 conversion, use pnpm CLI v9.
- pnpm test now passes all parameters after the test keyword directly to the underlying script. This matches the behavior of pnpm run test. Previously you needed to use the -- prefix. Related PR: #8619
node-gyp updated to version 11.
pnpm deploy now tries creating a dedicated lockfile from a shared lockfile for deployment. It will fallback to deployment without a lockfile if there is no shared lockfile or force-legacy-deploy is set to true.

Minor Changes

Added support for a new type of dependencies called "config dependencies". These dependencies are installed before all the other types of dependencies (before "dependencies", "devDependencies", "optionalDependencies").

Config dependencies cannot have dependencies of their own or lifecycle scripts. They should be added using exact version and the integrity checksum. Example:
```
{
  "pnpm": {
    "configDependencies": {
      "my-configs": "1.0.0+sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw=="
    }
  }
}
```
Related RFC: #8. Related PR: #8915.
New settings:
- New verify-deps-before-run setting. This setting controls how pnpm checks node_modules before running scripts:
  - install: Automatically run pnpm install if node_modules is outdated.
  - warn: Print a warning if node_modules is outdated.
  - prompt: Prompt the user to confirm running pnpm install if node_modules is outdated.
  - error: Throw an error if node_modules is outdated.
  - false: Disable dependency checks. Related Issue: #8585
- New inject-workspace-packages setting enables hard-linking all local workspace dependencies instead of symlinking them. Previously, this could be achieved using dependenciesMeta[].injected, which remains supported. Related PR: #8836
Faster repeat installs:

On repeated installs, pnpm performs a quick check to ensure node_modules is up to date. Related PR: #8838
pnpm add integrates with default workspace catalog:

When adding a dependency, pnpm add checks the default workspace catalog. If the dependency and version requirement match the catalog, pnpm add uses the catalog: protocol. Without a specified version, it matches the catalog’s version. If it doesn’t match, it falls back to standard behavior. Related Issue: #8640
pnpm dlx now resolves packages to their exact versions and uses these exact versions for cache keys. This ensures pnpm dlx always installs the latest requested packages. Related PR: #8811
No node_modules validation on certain commands. Commands that should not modify node_modules (e.g., pnpm install --lockfile-only) no longer validate or purge node_modules. Related PR: #8657

Platinum Sponsors

Gold Sponsors

Open source →

10.0.0-rc.35 Jan 2025pre-releaseBreaking

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to…

Major Changes

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the pnpm.onlyBuiltDependencies field of package.json #8897. For example:
```
{
  "pnpm": {
    "onlyBuiltDependencies": ["fsevents"]
  }
}
```
pnpm link behavior updated:

The pnpm link command now adds overrides to the root package.json.
- In a workspace: The override is added to the root of the workspace, linking the dependency to all projects in the workspace.
- Global linking: To link a package globally, run pnpm link from the package’s directory. Previously, you needed to use pnpm link -g. Related PR: #8653
Secure hashing with SHA256:

Various hashing algorithms have been updated to SHA256 for enhanced security and consistency:
- Long paths inside node_modules/.pnpm are now hashed with SHA256.
- Long peer dependency hashes in the lockfile now use SHA256 instead of MD5. (This affects very few users since these are only used for long keys.)
- The hash stored in the packageExtensionsChecksum field of pnpm-lock.yaml is now SHA256.
- The side effects cache keys now use SHA256.
- The pnpmfile checksum in the lockfile now uses SHA256 (#8530).
Configuration updates:
- manage-package-manager-versions: enabled by default. pnpm now manages its own version based on the packageManager field in package.json by default.
- public-hoist-pattern: nothing is hoisted by default. Packages containing eslint or prettier in their name are no longer hoisted to the root of node_modules. Related Issue: #8378
- Upgraded @yarnpkg/extensions to v2.0.3. This may alter your lockfile.
- virtual-store-dir-max-length: the default value on Windows has been reduced to 60 characters.
- Reduced environment variables for scripts: During script execution, fewer npm_package_* environment variables are set. Only name, version, bin, engines, and config remain. Related Issue: #8552
- All dependencies are now installed even if NODE_ENV=production. Related Issue: #8827
Changes to the global store:
- Store version bumped to v10.
- Some registries allow identical content to be published under different package names or versions. To accommodate this, index files in the store are now stored using both the content hash and package identifier.
  
  This approach ensures that we can:
  1. Validate that the integrity in the lockfile corresponds to the correct package, which might not be the case after a poorly resolved Git conflict.
  2. Allow the same content to be referenced by different packages or different versions of the same package. Related PR: #8510 Related Issue: #8204
- More efficient side effects indexing. The structure of index files in the store has changed. Side effects are now tracked more efficiently by listing only file differences rather than all files. Related PR: #8636
- A new index directory stores package content mappings. Previously, these files were in files.
Other breaking changes:
- The # character is now escaped in directory names within node_modules/.pnpm. Related PR: #8557
- Running pnpm add --global pnpm or pnpm add --global @pnpm/exe now fails with an error message, directing you to use pnpm self-update instead. Related PR: #8728
- Dependencies added via a URL now record the final resolved URL in the lockfile, ensuring that any redirects are fully captured. Related Issue: #8833
- The pnpm deploy command now only works in workspaces that have inject-workspace-packages=true. This limitation is introduced to allow us to create a proper lockfile for the deployed project using the workspace lockfile.
- Removed conversion from lockfile v6 to v9. If you need v6-to-v9 conversion, use pnpm CLI v9.
- pnpm test now passes all parameters after the test keyword directly to the underlying script. This matches the behavior of pnpm run test. Previously you needed to use the -- prefix. Related PR: #8619
node-gyp updated to version 11.
pnpm deploy now tries creating a dedicated lockfile from a shared lockfile for deployment. It will fallback to deployment without a lockfile if there is no shared lockfile or force-legacy-deploy is set to true.

Minor Changes

Added support for a new type of dependencies called "configurational dependencies". These dependencies are installed before all the other types of dependencies (before "dependencies", "devDependencies", "optionalDependencies").

Configurational dependencies cannot have dependencies of their own or lifecycle scripts. They should be added using exact version and the integrity checksum. Example:
```
{
  "pnpm": {
    "configDependencies": {
      "my-configs": "1.0.0+sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw=="
    }
  }
}
```
Related RFC: #8. Related PR: #8915.
New settings:
- New verify-deps-before-run setting. This setting controls how pnpm checks node_modules before running scripts:
  - install: Automatically run pnpm install if node_modules is outdated.
  - warn: Print a warning if node_modules is outdated.
  - prompt: Prompt the user to confirm running pnpm install if node_modules is outdated.
  - error: Throw an error if node_modules is outdated.
  - false: Disable dependency checks. Related Issue: #8585
- New inject-workspace-packages setting enables hard-linking all local workspace dependencies instead of symlinking them. Previously, this could be achieved using dependenciesMeta[].injected, which remains supported. Related PR: #8836
Faster repeat installs:

On repeated installs, pnpm performs a quick check to ensure node_modules is up to date. Related PR: #8838
pnpm add integrates with default workspace catalog:

When adding a dependency, pnpm add checks the default workspace catalog. If the dependency and version requirement match the catalog, pnpm add uses the catalog: protocol. Without a specified version, it matches the catalog’s version. If it doesn’t match, it falls back to standard behavior. Related Issue: #8640
pnpm dlx now resolves packages to their exact versions and uses these exact versions for cache keys. This ensures pnpm dlx always installs the latest requested packages. Related PR: #8811
No node_modules validation on certain commands. Commands that should not modify node_modules (e.g., pnpm install --lockfile-only) no longer validate or purge node_modules. Related PR: #8657

Platinum Sponsors

Gold Sponsors

Open source →

10.0.0-rc.229 Dec 2024pre-releaseBreaking

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to…

Major Changes

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the pnpm.onlyBuiltDependencies field of package.json #8897. For example:
```
{
  "pnpm": {
    "onlyBuiltDependencies": ["fsevents"]
  }
}
```
pnpm link behavior updated:

The pnpm link command now adds overrides to the root package.json.
- In a workspace: The override is added to the root of the workspace, linking the dependency to all projects in the workspace.
- Global linking: To link a package globally, run pnpm link from the package’s directory. Previously, you needed to use pnpm link -g. Related PR: #8653
Secure hashing with SHA256:

Various hashing algorithms have been updated to SHA256 for enhanced security and consistency:
- Long paths inside node_modules/.pnpm are now hashed with SHA256.
- Long peer dependency hashes in the lockfile now use SHA256 instead of MD5. (This affects very few users since these are only used for long keys.)
- The hash stored in the packageExtensionsChecksum field of pnpm-lock.yaml is now SHA256.
- The side effects cache keys now use SHA256.
- The pnpmfile checksum in the lockfile now uses SHA256 (#8530).
Configuration updates:
- manage-package-manager-versions: enabled by default. pnpm now manages its own version based on the packageManager field in package.json by default.
- public-hoist-pattern: nothing is hoisted by default. Packages containing eslint or prettier in their name are no longer hoisted to the root of node_modules. Related Issue: #8378
- Upgraded @yarnpkg/extensions to v2.0.3. This may alter your lockfile.
- virtual-store-dir-max-length: the default value on Windows has been reduced to 60 characters.
- Reduced environment variables for scripts: During script execution, fewer npm_package_* environment variables are set. Only name, version, bin, engines, and config remain. Related Issue: #8552
- All dependencies are now installed even if NODE_ENV=production. Related Issue: #8827
Changes to the global store:
- Store version bumped to v10.
- Some registries allow identical content to be published under different package names or versions. To accommodate this, index files in the store are now stored using both the content hash and package identifier.
  
  This approach ensures that we can:
  1. Validate that the integrity in the lockfile corresponds to the correct package, which might not be the case after a poorly resolved Git conflict.
  2. Allow the same content to be referenced by different packages or different versions of the same package. Related PR: #8510 Related Issue: #8204
- More efficient side effects indexing. The structure of index files in the store has changed. Side effects are now tracked more efficiently by listing only file differences rather than all files. Related PR: #8636
- A new index directory stores package content mappings. Previously, these files were in files.
Other breaking changes:
- The # character is now escaped in directory names within node_modules/.pnpm. Related PR: #8557
- Running pnpm add --global pnpm or pnpm add --global @pnpm/exe now fails with an error message, directing you to use pnpm self-update instead. Related PR: #8728
- Dependencies added via a URL now record the final resolved URL in the lockfile, ensuring that any redirects are fully captured. Related Issue: #8833
- The pnpm deploy command now only works in workspaces that have inject-workspace-packages=true. This limitation is introduced to allow us to create a proper lockfile for the deployed project using the workspace lockfile.
- Removed conversion from lockfile v6 to v9. If you need v6-to-v9 conversion, use pnpm CLI v9.
- pnpm test now passes all parameters after the test keyword directly to the underlying script. This matches the behavior of pnpm run test. Previously you needed to use the -- prefix. Related PR: #8619
node-gyp updated to version 11.
pnpm deploy now tries creating a dedicated lockfile from a shared lockfile for deployment. It will fallback to deployment without a lockfile if there is no shared lockfile or force-legacy-deploy is set to true.

Minor Changes

New settings:
- New verify-deps-before-run setting. This setting controls how pnpm checks node_modules before running scripts:
  - install: Automatically run pnpm install if node_modules is outdated.
  - warn: Print a warning if node_modules is outdated.
  - prompt: Prompt the user to confirm running pnpm install if node_modules is outdated.
  - error: Throw an error if node_modules is outdated.
  - false: Disable dependency checks. Related Issue: #8585
- New inject-workspace-packages setting enables hard-linking all local workspace dependencies instead of symlinking them. Previously, this could be achieved using dependenciesMeta[].injected, which remains supported. Related PR: #8836
Faster repeat installs:

On repeated installs, pnpm performs a quick check to ensure node_modules is up to date. Related PR: #8838
pnpm add integrates with default workspace catalog:

When adding a dependency, pnpm add checks the default workspace catalog. If the dependency and version requirement match the catalog, pnpm add uses the catalog: protocol. Without a specified version, it matches the catalog’s version. If it doesn’t match, it falls back to standard behavior. Related Issue: #8640
pnpm dlx now resolves packages to their exact versions and uses these exact versions for cache keys. This ensures pnpm dlx always installs the latest requested packages. Related PR: #8811
No node_modules validation on certain commands. Commands that should not modify node_modules (e.g., pnpm install --lockfile-only) no longer validate or purge node_modules. Related PR: #8657

Platinum Sponsors

Gold Sponsors

Open source →

10.0.0-rc.127 Dec 2024pre-releaseBreaking

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to…

Major Changes

Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the pnpm.onlyBuiltDependencies field of package.json #8897. For example:
```
{
  "pnpm": {
    "onlyBuiltDependencies": ["fsevents"]
  }
}
```
pnpm link behavior updated:

The pnpm link command now adds overrides to the root package.json.
- In a workspace: The override is added to the root of the workspace, linking the dependency to all projects in the workspace.
- Global linking: To link a package globally, run pnpm link from the package’s directory. Previously, you needed to use pnpm link -g. Related PR: #8653
Secure hashing with SHA256:

Various hashing algorithms have been updated to SHA256 for enhanced security and consistency:
- Long paths inside node_modules/.pnpm are now hashed with SHA256.
- Long peer dependency hashes in the lockfile now use SHA256 instead of MD5. (This affects very few users since these are only used for long keys.)
- The hash stored in the packageExtensionsChecksum field of pnpm-lock.yaml is now SHA256.
- The side effects cache keys now use SHA256.
- The pnpmfile checksum in the lockfile now uses SHA256 (#8530).
Configuration updates:
- manage-package-manager-versions: enabled by default. pnpm now manages its own version based on the packageManager field in package.json by default.
- public-hoist-pattern: nothing is hoisted by default. Packages containing eslint or prettier in their name are no longer hoisted to the root of node_modules. Related Issue: #8378
- Upgraded @yarnpkg/extensions to v2.0.3. This may alter your lockfile.
- virtual-store-dir-max-length: the default value on Windows has been reduced to 60 characters.
- Reduced environment variables for scripts: During script execution, fewer npm_package_* environment variables are set. Only name, version, bin, engines, and config remain. Related Issue: #8552
- All dependencies are now installed even if NODE_ENV=production. Related Issue: #8827
Changes to the global store:
- Store version bumped to v10.
- Some registries allow identical content to be published under different package names or versions. To accommodate this, index files in the store are now stored using both the content hash and package identifier.
  
  This approach ensures that we can:
  1. Validate that the integrity in the lockfile corresponds to the correct package, which might not be the case after a poorly resolved Git conflict.
  2. Allow the same content to be referenced by different packages or different versions of the same package. Related PR: #8510 Related Issue: #8204
- More efficient side effects indexing. The structure of index files in the store has changed. Side effects are now tracked more efficiently by listing only file differences rather than all files. Related PR: #8636
- A new index directory stores package content mappings. Previously, these files were in files.
Other breaking changes:
- The # character is now escaped in directory names within node_modules/.pnpm. Related PR: #8557
- Running pnpm add --global pnpm or pnpm add --global @pnpm/exe now fails with an error message, directing you to use pnpm self-update instead. Related PR: #8728
- Dependencies added via a URL now record the final resolved URL in the lockfile, ensuring that any redirects are fully captured. Related Issue: #8833
- The pnpm deploy command now only works in workspaces that have inject-workspace-packages=true. This limitation is introduced to allow us to create a proper lockfile for the deployed project using the workspace lockfile.
- Removed conversion from lockfile v6 to v9. If you need v6-to-v9 conversion, use pnpm CLI v9.
- pnpm test now passes all parameters after the test keyword directly to the underlying script. This matches the behavior of pnpm run test. Previously you needed to use the -- prefix. Related PR: #8619
node-gyp updated to version 11.

Minor Changes

New settings:
- New verify-deps-before-run setting. This setting controls how pnpm checks node_modules before running scripts:
  - install: Automatically run pnpm install if node_modules is outdated.
  - warn: Print a warning if node_modules is outdated.
  - prompt: Prompt the user to confirm running pnpm install if node_modules is outdated.
  - error: Throw an error if node_modules is outdated.
  - false: Disable dependency checks. Related Issue: #8585
- New inject-workspace-packages setting enables hard-linking all local workspace dependencies instead of symlinking them. Previously, this could be achieved using dependenciesMeta[].injected, which remains supported. Related PR: #8836
Faster repeat installs:

On repeated installs, pnpm performs a quick check to ensure node_modules is up to date. Related PR: #8838
pnpm add integrates with default workspace catalog:

When adding a dependency, pnpm add checks the default workspace catalog. If the dependency and version requirement match the catalog, pnpm add uses the catalog: protocol. Without a specified version, it matches the catalog’s version. If it doesn’t match, it falls back to standard behavior. Related Issue: #8640
pnpm dlx now resolves packages to their exact versions and uses these exact versions for cache keys. This ensures pnpm dlx always installs the latest requested packages. Related PR: #8811
No node_modules validation on certain commands. Commands that should not modify node_modules (e.g., pnpm install --lockfile-only) no longer validate or purge node_modules. Related PR: #8657

Platinum Sponsors

Gold Sponsors

Open source →