NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #466 most downloaded on npm
Fast, disk space efficient package manager
Latest stable
12.23.0
Last release today
22 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 57 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
1370 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Platform variants are removed, so packages that publish them need to move to optionalDependencies . It also carries security fixes: pnpm no longer rea…
This release adds pnpm edit, pnpm catalog migrate, and pnpm link --hard, and moves deprecation warnings into the install summary. Platform variants are removed, so packages that publish them need to move to optionalDependencies. It also carries security fixes: pnpm no longer reads otp from config files, and it sends registry credentials only over HTTPS.
Removed platform variants. A package version has one archive again.
pnpm no longer reads publishConfig.variants or the variant field of package.json. pnpm pack --variant and the --upload-variant, --variant-integrity and --no-variants options of pnpm publish are gone. pnpr no longer accepts variant archives with a version or serves them at <name>@<version>/variants/<tag>.
To ship builds for several platforms, publish each as its own package and list them in optionalDependencies. A frozen install of a lockfile that records the variants of a registry package fails with ERR_PNPM_BROKEN_LOCKFILE. Run pnpm install to resolve the lockfile again.
pnpm pack and pnpm publish now fail if a package that is not private lists a private workspace package in dependencies. A private package is never published, so the published package could not be installed. devDependencies, optionalDependencies, peerDependencies, and bundled dependencies are still allowed #2321.
pnpm publish now supports --new-version <version>, which sets the version in package.json before publishing. With --recursive, every selected workspace package is set to the new version #2168.
pnpm pack --json now reports the package.json that goes into the tarball, with publishConfig and the other publish-time changes applied. Run pnpm pack --dry-run --json to preview it without writing a tarball. A dry run still runs prepack and prepare, unless --ignore-scripts is passed.
pnpm pack and pnpm publish now add a workspace-root COPYING file to a workspace package that has no license file. A COPYING file at the package root now counts as the package's license, so the workspace-root LICENSE is no longer added next to it.
Added the versioning.includePrivatePackages setting. Set it to false to leave private packages out of pnpm change #13813.
Added the pnpm edit command to open an installed package directory in an editor.
Added pnpm catalog migrate, which moves dependency specifiers into the default catalog and replaces them in the workspace projects' package.json files with catalog:. A dependency moves only when every project declares it with the same specifier. The command lists the dependencies it leaves unchanged #7072.
Added a --hard option to pnpm link. With --hard, pnpm saves the linked package with the file: protocol, so its files are hard linked into node_modules and its dependencies and peer dependencies resolve from your project. pnpm unlink removes these links too #9895.
pnpm remove now accepts glob patterns and ! exclusions in dependency selectors, such as pnpm remove "eslint-*" "!eslint-plugin-import" #13546.
When pnpm updates a package.json5, it now changes only the values that changed. Comments, quotes, number formats, and layout elsewhere in the file stay as written. New keys and strings use the quote style of the file.
nodeLinker accepts object settings for isolated and hoisted installs. Linker-specific hoisting options can be configured alongside the selected linker.
pnpm update --latest <pkg> now moves the override that pins the named dependency #8701. pnpm update --interactive --latest does the same for every selected dependency. An override keeps its own range shape: a pin on an exact version lands on the new exact version, and ^ stays ^. When pnpm cannot update the governing override automatically, the update prints a warning naming it.
pnpm update now accepts --tag <tag>. The flag updates the matched dependencies to the version behind the given dist-tag and rewrites the ranges in package.json, the way --latest updates to the latest tag. It also works with --interactive and with global updates #3534.
With trustPolicy: no-downgrade, pnpm update --interactive shows a Trust column with the trust evidence of each offered registry dependency #8889. The list also offers only versions the trust policy accepts, so it matches what the update installs.
pnpm update --interactive --long shows the homepage or repository URL of each package. The URL column is hidden without --long.
Added the referenceTime setting. minimumReleaseAge and trustPolicyIgnoreAfter count back from this RFC 3339 time, both when pnpm resolves versions and when it verifies a lockfile. Set it in pnpm-workspace.yaml or with PNPM_CONFIG_REFERENCE_TIME.
Added the --minimum-release-age and --minimum-release-age-exclude options to pnpm install, pnpm add, pnpm update, and pnpm dlx. They set minimumReleaseAge and minimumReleaseAgeExclude for a single run without editing a config file #11224.
pnpm audit --fix accepts --no-add-release-age-exclusions, which applies the fixes without adding entries to minimumReleaseAgeExclude.
--allow-build now accepts a comma-separated list of packages, so pnpm add foo bar --allow-build=foo,bar is the same as passing --allow-build=foo --allow-build=bar #9560.
Deprecation warnings moved into the install summary and only name the packages the install added. A deprecated dependency added by the install is marked deprecated on its summary line, with the version that is not deprecated when there is one. Deprecated subdependencies the install added are listed right after the summary. Deprecated packages that were already installed are reported as one count, such as 3 deprecated packages are still installed.
In a workspace, the install summary now lists the direct dependency changes of every project, not only of the project pnpm runs in. Each change is listed once, followed by the projects that made it, unless only the current project did. A project's first install lists only deprecated or outdated dependencies and the ones the command added #6481.
pnpm install now warns when an entry in overrides matches no dependency, in a single line such as 2 overrides matched no dependency: foo, parent>child. Only the overrides declared in the workspace are checked. Overrides added by a config dependency or an updateConfig hook are not. Set warnUnusedOverrides: false to turn the warning off #10315.
pnpm install now shows lockfile verification progress while the supply-chain check runs. The final pass or failure line reports how many entries were checked.
pnpm doctor now checks the environment that lifecycle scripts run in. It lists the node executables on PATH and warns about broken ones. It reports the shell that runs scripts. A new check runs a package's executable from a script, both in a temporary project and in the current project. If that script fails, the report includes the error and, outside Windows, a trace of the executable's shim that shows how it looked up and started node #16308.
pnpm self-update, pnpm setup, and the "Install method" check of pnpm doctor now warn when another pnpm on PATH would run in place of the one pnpm installed. The warning names that copy. If pnpm recognizes how it was installed (npm, Homebrew, Corepack, Volta, or Scoop), the warning also gives the command that removes it.
Set PNPM_CONFIG_HOME to choose the directory containing config.yaml and auth.ini. Global configuration commands read and write files in this directory. A non-empty value takes precedence over XDG_CONFIG_HOME and the platform defaults.
pnpm now provides a prebuilt binary for Linux on LoongArch (loong64) with glibc.
A failed devEngines.runtime or engines.runtime check now reports the reason in its error code. A runtime that is not installed fails with ERR_PNPM_RUNTIME_NOT_FOUND. A runtime entry without a version range fails with ERR_PNPM_MISSING_RUNTIME_VERSION_RANGE, and one with an invalid range fails with ERR_PNPM_INVALID_RUNTIME_VERSION_RANGE. An installed version that does not satisfy the range still fails with ERR_PNPM_BAD_RUNTIME_VERSION.
pnpm view <pkg> now prints the registry it read the metadata from at the end of the summary #11394.
otp is no longer read from any config file. Pass --otp on the command line, or set PNPM_CONFIG_OTP. A pnpm-workspace.yaml or a global config.yaml that carries otp is ignored, with a warning naming those two channels. pnpm config set otp fails with ERR_PNPM_CONFIG_SET_NOT_A_FILE_SETTING.
This closes a way to leak a secret. A repository could write otp: ${NPM_TOKEN} beside its own registry:, and pnpm publish sent that environment variable to the registry the same file named, in the npm-otp header of its first request #13542.
pnpm now sends registry credentials only over HTTPS or loopback HTTP, both for tarball downloads and for requests to pnprServer. Tarball and package metadata requests respect registry credential paths on redirects. A failed tarball request can no longer pin its redirect destination in the lockfile.
pnpm install now rejects local filesystem dependencies (file:, link:, and path-based workspace: specifiers) declared by non-local packages with ERR_PNPM_LOCAL_SUBDEP_NOT_ALLOWED. Relative file: dependencies inside a package's own archive and local dependencies configured by the workspace through overrides, packageExtensions, or .pnpmfile.cjs continue to work. Lockfile verification also rejects unauthorized local directory, tarball, and link entries on non-importer snapshots.
pnpm install and pnpm install --frozen-lockfile now enforce blockExoticSubdeps against entries in pnpm-lock.yaml. Before, pnpm accepted a lockfile with git or tarball URL subdependencies and installed those packages even with blockExoticSubdeps: true.
pnpm install with pnprServer now rejects registry-keyed lockfile entries whose resolution uses a non-registry source with ERR_PNPM_RESOLUTION_SHAPE_MISMATCH. The pnpr lockfile verification and resolution endpoints enforce the same check before accepting or caching a lockfile.
pnpm dlx, pnx, and pnpm create now ignore local configuration in the working directory. This covers .pnpmfile.cjs hooks, proxy and TLS settings in the project .npmrc, and execution, layout, and resolution settings in a local pnpm-workspace.yaml, including pnpmfile, globalPnpmfile, configDependencies, scriptShell, cacheDir, storeDir, and ignoreScripts. Settings from the user's global config.yaml, such as blockExoticSubdeps, cacheDir, and storeDir, remain active.
Global commands (--global, -g) no longer load .pnpmfile.cjs, pnpm-workspace.yaml, or .npmrc from the current working directory. pnpm why -g now inspects globally installed packages.
pnpm config get refuses to print protected auth settings. pnpm config list hides TLS private keys and inline proxy credentials. pnpm config set --global tokenHelper writes to auth.ini, and setting a project-level tokenHelper fails.
TLS file paths in .npmrc and auth.ini resolve relative to the file that declares them. Project .npmrc files skip TLS file paths containing environment variables.
When the pnpm package downloads its native binary on first run, it now handles registry credentials the way pnpm does:
//registry.example.com/org-a/npm/:_authToken, are sent only to that path. They were sent to any path on the same host.auth.ini, where pnpm login writes them, and from the _auth setting of the global config.yaml.${NPM_TOKEN?} placeholder in .npmrc expands to the variable. It expanded to an empty value, so the download was sent without credentials.Matching a glob that repeats a wildcard, such as +(*)z in the workspace packages patterns, no longer hangs on long paths. The bundled picomatch is patched for a security advisory.
pnpm pack and pnpm publish now reject publishConfig.directory values that use an absolute path or .. segments outside the package directory.
The pnpm binary no longer depends on chrono, which RustSec reports as unmaintained in RUSTSEC-2026-0543.
pnpm install now adds a new workspace package that has no dependencies to the importers of pnpm-lock.yaml #18189.
With enableGlobalVirtualStore on, require.extensions hooks run again for require() calls from a module compiled from a string, such as the module Next.js uses to load next.config.ts. A required .ts file skipped the registered TypeScript hook. A required .json file was parsed as JavaScript #18261.
On Windows, when the project is on a network share, pnpm install now links dependencies in node_modules with the kind of link that can be opened on that share. It tries a junction first and a symlink second. If neither can be opened, the install fails with advice.
On Windows, concurrent installs that link the same dependency no longer leave an .ignored_<name> entry next to the link in the global virtual store.
pnpm install now fails with ERR_PNPM_UNSUPPORTED_PROTOCOL when a file: dependency that is not a workspace project uses a catalog: specifier. Injected workspace projects still resolve their catalog: dependencies.
A link: or relative-path dependency of a local directory dependency now resolves from that directory. In any other package, such as a local tarball, it resolves from the lockfile directory. Both used to resolve from the importing project's directory pnpm/tasks#319.
Two workspace projects that declare the same injected relative-path dependency, such as ../child, no longer share the directory the first one resolved.
pnpm install now links a workspace package for a workspace: range that combines ^, ~, or * with other ranges, such as workspace:^ || ^2.0.0.
Fixed pnpm install keeping a runtime binary for the previous platform after a change to supportedArchitectures with the global virtual store disabled.
The nodeVersion setting no longer changes the global virtual store directory names or the side-effects cache keys. These follow the Node.js runtime that pnpm installs for the project, then the node on PATH. pnpm licenses and pnpm store status now find packages that an install with nodeVersion placed in the global virtual store.
Fixed package maps resolving workspace and linked packages to the wrong directory when a path contains #, ?, or %.
pnpm install and pnpm peers check no longer report a catalog: peer of an injected workspace package as unmet when the installed version matches the catalog entry #10279.
The peer dependency check now reads the version of an injected workspace package from its package.json. pnpm install with strictPeerDependencies: true and pnpm peers check no longer report such a peer as unmet with a file: version.
With sharedWorkspaceLockfile: false, pnpm install now reports missing peers of linked workspace packages, as pnpm peers check does.
peerDependencyRules.allowedVersions now accepts a parent version range that contains >, such as "foo@>=1.0.0>bar": "1".
Fixed nodeLinker: hoisted installs in a workspace where the directory of one project is inside the directory of another. A dependency of the inner project could resolve to the version in the outer project's node_modules. pnpm now keeps the inner project's dependency in its own node_modules when the outer project holds another version.
With nodeLinker: hoisted, pnpm now finds the agent skills of a dependency whose directory is shared with another peer variant of the same package version.
pnpm install with pnprServer set now handles more workspace settings:
injectWorkspacePackages, dedupeInjectedDeps, ignoredOptionalDependencies, and dependenciesMeta. Projects that use them no longer fail with ERR_PNPM_OUTDATED_LOCKFILE or ERR_PNPM_LOCKFILE_CONFIG_MISMATCH.pnpm install --update-checksums refreshes the integrity checksums in the lockfile.minimumReleaseAgeStrict and adds fallback versions to minimumReleaseAgeExclude when strict mode is off.file:, link:, or local path dependencies, or when blockExoticSubdeps is false. pnpr also rejects local filesystem dependency specifiers on /-/pnpr/v0/resolve.When an overrides entry requests a version that does not exist on the registry, pnpm install now names that override entry in the error. If the entry's selector has a version range, such as foo@^1, the error also shows the latest published version in that range.
pnpm add run from a workspace package directory that has no package.json yet now suggests creating one with pnpm init #11345.
The install summary now shows "(X is available)" after a direct dependency whose latest version on the registry is newer than the one installed. The note appears when the install resolved that dependency against registry metadata.
Approving the minimumReleaseAge prompt no longer reprints the list of packages it just showed. pnpm now confirms with one line that says how many entries it added to minimumReleaseAgeExclude #15377.
pnpm now prints a warning that explains why it has to remove and recreate a modules directory.
pnpm install with nodeLinker: hoisted no longer hangs or runs out of memory in large workspaces whose packages are installed with many different sets of peer dependencies.
Sped up pnpm install on macOS for packages installed with several sets of peer dependencies. pnpm now clones every peer variant of a package from one cached copy of its files.
Sped up linking bins in large workspaces. pnpm now reuses a workspace package's package.json across the projects that depend on it when linking their bins.
pnpm install --frozen-lockfile no longer waits for a Node.js version check it does not use before it exits. With Homebrew's Node.js, a frozen install with nothing to do can be about 3x faster.
Resolving a remote tarball uses the download response directly, saving a request.
pnpm in StackBlitz WebContainers sends HTTP response bodies and subprocess output to its engine as raw bytes. A 64 KiB chunk no longer becomes a 234 KB message pnpm/tasks#63.
Fixed pnpm install failing with ERR_PNPM_NEXT_LOCKFILE_NOT_REPRESENTABLE under lockfile.format: v13 when a peer dependency is provided by an aliased package and another alias installs the package that has the peer's name #18198.
Fixed writing v13 lockfiles when a package has an ordinary npm alias of one of its direct or transitive peers #18274.
Fixed conversion to the v13 lockfile format when a hashed peer suffix includes a workspace link and the package installs its own copy of another declared peer #18288.
pnpm install now converts an existing lockfile when you change lockfile.format, even when all dependencies are already installed. With lockfile.format: v13, an install that updates a v9 lockfile without resolving, for example after a dependency is removed, now writes the v13 format.
A lockfile in the experimental v13 format now always records autoDedupe, dedupeInjectedDeps, dedupePeerDependents and linkWorkspacePackages, as lockfile.includeResolutionSettings does for the v9 format. After pnpm install --frozen-lockfile with autoDedupe, pnpm run no longer starts another install. Run pnpm install once to record the settings in a v13 lockfile written by an earlier version, since pnpm install --frozen-lockfile fails on it #16583.
pnpm install --frozen-lockfile now checks the dependencies of local directory dependencies against the lockfile more closely. It fails when the injected setting of such a dependency no longer matches the lockfile pnpm/tasks#319. It accepts a plain-range dependency that linkWorkspacePackages: deep linked to a workspace project.
Frozen installs now detect changes to catalog entries used only by peer dependencies of local directory packages.
Frozen installs now restore links declared through catalogs when excludeLinksFromLockfile is enabled.
pnpm install --frozen-lockfile now revalidates registry metadata when verifying a locked tarball whose version is missing from the cached package listing.
During dependency filtering in commands such as pnpm install --prod --frozen-lockfile, pnpm now recovers hashed peers in v9 lockfiles only when a binding can affect which dependencies are kept #18276.
Fixed pnpm install --lockfile-only fetching a locked transitive Git dependency when an unrelated dependency changes #18217.
Fixed pnpm fetch failing when a Docker build copies the lockfile before the workspace configuration or pnpmfile.
pnpm-lock.yaml now quotes strings that look like numbers, such as +.5, so they are read back as strings.
pnpm approve-builds --all and pnpm approve --all no longer approve a package whose build is denied with false in pnpm-workspace.yaml.
A <pkg>@<version>: false entry in allowBuilds or permissions now also blocks <pkg>@<version> from a named registry, including when dangerouslyAllowAllBuilds is set.
pnpm add --allow-build now records its decision under permissions when pnpm-workspace.yaml has a permissions setting. Before, a --allow-build=!<pkg> denial went to allowBuilds and was overridden by an existing permissions.<pkg>.build: true.
pnpm approve-builds now requires the exact selector shown by pnpm ignored-builds for a dependency a bare package name cannot identify (a file:, git, or tarball artifact). A bare package name only approves a plain registry version #18237.
pnpm approve-builds, pnpm approve, and pnpm add --allow-build now refuse to edit a package's permissions entry written as an inline mapping that spans several lines. Before, they added a second key for the package to pnpm-workspace.yaml.
Install now reports packages awaiting build and skill approval in one notice. Approval prompts and notices show a package from a named registry by its name. They no longer label it as a tarball.
Fixed pnpm run hanging after an interrupt:
pnpm run and pnpm exec no longer trigger a reinstall solely because the last install used --trust-lockfile #18218.
The workspace project graph now follows overrides. An override that points a dependency at a workspace package, such as foo: workspace:*, makes that package a dependency of every project whose declaration the override matches, even with linkWorkspacePackages off. pnpm install now runs that package's lifecycle scripts before the scripts of the projects depending on it. pnpm -r run orders the projects the same way. --filter selectors that follow dependencies now see the edge.
A [<since>] filter such as --filter "...[origin/main]" now selects a project whose dependency an overrides entry points at a changed catalog entry. For example, with lib: catalog:local in overrides, changing lib in the local catalog selects every project that depends on lib.
When sharedWorkspaceLockfile is false, pnpm install now runs the workspace root's pnpm:devPreinstall script once, before any project is installed, including when a filter excludes the root. Workspace members no longer run theirs #4503.
Recursive runs honor --sequential with --parallel, and changed-file ignore patterns support negation. pnpm list -r --no-sort --reverse reverses the selected project order. pnpm clean forwards positional arguments to a project's clean script.
--resume-from starts at the named project when the previous run completed no tasks.
pnpm pipeline fixes:
--env-file, extraEnv, or NODE_OPTIONS change, or when the script shell settings change.! exclusions.--filter and --filter-prod, includes untracked files when selecting affected projects, and runs the prerequisites of tasks matched by regex selectors.fingerprint or .fingerprint directory in a nested Cargo build.With shellEmulator: true, parameter expansions such as ${MODE:-dev} now see assignments made earlier in the script.
Plug'n'Play fixes:
require.resolve() lookup paths.NODE_OPTIONS and command-line flags, and respects Node.js's enabled node-addons and module-sync conditions.pnpm run and pnpm exec, including recursive runs, find the loader and the experimental package map when lockfileDir is configured.pnpm install recreates a deleted .pnp.cjs loader, and a full pnpm clean removes the generated loader.After a workspace script runs, pnpm links commands from scoped injected packages into the containing modules directory's .bin. Commands declared through directories.bin are also refreshed.
Refreshing injected dependencies preserves the install's NODE_PATH settings in command shims and respects workspace package exclusions.
pnpm recognizes uppercase file extensions when choosing the interpreter for commands without a shebang. It skips hidden files and directories when linking commands from directories.bin.
pnpm dlx, pnx, and pnpm create now handle script skipping and non-registry package specifiers consistently:
--ignore-scripts or ignoreScripts: true uses a separate dlx cache key, keeping cached installs that skipped build scripts separate from normal runs../my-cli and ./my-cli.tgz resolve against the caller's working directory.file:, and git URL packages run their build scripts by default unless --ignore-scripts or a negated --allow-build selector disables them.A tasks entry with no value in pnpm-workspace.yaml, such as build:, now fails with a hint. The hint suggests writing {} for a task with no settings, or removing the entry to keep the default dependsOn: ['^<task>'].
pnpm install now locks Cargo path dependencies outside the workspace, as Cargo does. It failed with workspace dependency <name> is not a workspace member. pnpm install --frozen-lockfile now also fails when Cargo.lock misses a path dependency or locks a git dependency at another branch, tag, or revision.
pnpm outdated and pnpm update now include Cargo dependencies declared under [target.<cfg>.dependencies]. pnpm update --prod no longer fails on a crate that is also a dev-dependency. pnpm add crate: fails in a virtual Cargo workspace root, as cargo add does. It added a [dependencies] table that Cargo rejects there.
pnpm remove accepts Python and Cargo package specifiers. Recursive and filtered updates include standalone Python and Cargo workspace members. pnpm update and pnpm outdated match normalized Python names and Cargo aliases.
pnpm install now skips a Python project that has only a requirements.txt when its directory has a .venv that pnpm did not create, and prints a warning. The install failed for the whole workspace before.
Fixed Python wheel installs with legacy metadata, whitespace around entry point targets, and interpreter options in script shebangs.
Python dependency groups now match normalized names. Adding a development dependency reports when the project excludes the dev group.
Comments ending in a backslash in requirements.txt no longer hide the next requirement. pnpm exec finds the environment of requirements-only projects under a tool-only pyproject.toml.
Fixed pnpm add and pnpm update in shared Python workspaces that contain a requirements-only member.
Fixed pnpm update failing with a TOML parse error when pyproject.toml declares [project.optional-dependencies].
pnpm store prune no longer removes files of the wheels that an installed Python project uses, so pnpm install --offline can recreate its environment. Pruning now also removes the store index entries of Python and Cargo archives whose files it deleted.
pnpm audit now checks tarball, git, and named-registry dependencies against security advisories. pnpm audit signatures now verifies packages installed from named registries and skips non-registry dependencies.
pnpm audit now checks patched versions correctly when registry metadata includes an unpublished entry in its time field #18209.
pnpm audit --fix=true now applies the default override fix method, like a bare pnpm audit --fix #13261.
pnpm outdated now reports newer prereleases of an installed prerelease. It checks the dist-tag that points to the newest version of the installed prerelease channel, such as next for 3.0.0-rc.0, alongside latest #7339.
Fixed pnpm update and pnpm outdated matching every dependency of an ecosystem when a positive selector is combined with a negated package selector such as !lodash. This applied to Cargo, Python, npm, and --include-github-actions selectors.
Fixed pnpm update and pnpm outdated with --include-github-actions corrupting workflow YAML or skipping actions referenced through YAML anchors, aliases, or merge keys.
pnpm add and pnpm update now keep the range operator of a specifier that has both a prerelease and a build suffix, such as ^1.0.0-next.0+build.1.
pnpm dedupe --check no longer requests the registry metadata of locked versions that the cache already holds. pnpm dedupe skips those requests too when lockfile.format is v13, which records no deprecated notices. Both were slow against a registry that sends no ETag or Last-Modified, such as Azure Artifacts, where each request downloaded the full package metadata #17758.
pnpm publish now reads access and tag from pnpm-workspace.yaml, the global config.yaml, and PNPM_CONFIG_ACCESS / PNPM_CONFIG_TAG. The --access and --tag flags still win when set. A configured access outranks publishConfig.access. An empty publishBranch now allows master and main #13542.
pnpm pack and pnpm publish fixes:
publishConfig.name.package.yaml or package.json5 manifest are packed correctly, and these packages include their parked changelog.beforePacking is validated and normalized.pnpm version fixes:
1.2.3foo or 01.2.3. It used to set a normalized version that differed from the argument.--preid.pnpm version -r updates explicit workspace dependency ranges that a release invalidates.preversion script makes to other manifest fields.When pnpm unpublish removes the version tagged latest, it prefers the highest remaining stable version.
pnpm stage uses the current package's publish registry when listing, viewing, approving, rejecting, or downloading staged versions. To use a one-time password at a non-default registry selected by the package, pass --registry.
Fixed several bugs in patching dependencies:
diff --git lines now applies.ERR_PNPM_INVALID_PATCH. Before, pnpm wrote the symlink as a regular file.pnpm patch-commit --patches-dir ../outside now fails with ERR_PNPM_PATCHES_DIR_OUTSIDE_PROJECT. Before, pnpm wrote the patch to outside inside the project.pnpm patch-commit keeps a file without a final newline unterminated when that file comes last in the patch. Before, the patched file gained a trailing newline.pnpm patch-commit keeps the peers a patched package is bound to in the lockfile. It no longer fails with ERR_PNPM_NEXT_LOCKFILE_NOT_REPRESENTABLE when the package has an optional peer and lockfile.format is v13.patchedDependencies entry now records its patch hash on a file: directory dependency or an injected workspace package. pnpm install --frozen-lockfile no longer fails with ERR_PNPM_INCONSISTENT_PATCH_HASH on the lockfile that pnpm install wrote.pnpm patch and pnpm patch-commit find a package installed from a namedRegistries alias by its version. For example, pnpm patch foo@1.0.0 patches a dependency declared as work:1.0.0.pnpm patch-remove removes the corresponding edit directory and state entry from node_modules/.pnpm_patches.Global packages fixes:
pnpm add -g with several space-separated packages lists every installed package in its summary. Only the packages of the first one were listed.pnpm list -g with --depth greater than 0 always reads the global install directory's node_modules and lockfile. It could read the current project's lockfile or a custom modulesDir.pnpm add -g, pnpm update -g, and pnpm outdated -g use the _auth and npmrcAuthFile settings under globalPackagesConfig in the global config.yaml.dangerouslyAllowAllBuilds set at the top level of the global config.yaml. pnpm ignored it for global packages unless it was set under globalPackagesConfig.Fixed pnpm deploy for projects that depend on an external directory through link:. pnpm deploy now also resolves relative file: overrides from the source workspace #18191.
Fixed pnpm link for target manifests without a name. The command uses the directory name and normalizes relative paths written to the manifest. It also resolves a quoted ~/ path from the home directory.
Fixed pnpm prune leaving extraneous package links in hoisted installations, and pruneDirectDependencies skipping cleanup when the lockfile was already up to date.
pnpm import fixes:
sharedWorkspaceLockfile is disabled and lockfileDir is unset.disallowWorkspaceCycles and the symlink policy for the destination lockfile.pnpm store add now fails if it cannot write a package to the store index, for example when another process holds the index locked. It also indexes tarball URLs that have no integrity value #18194.
pnpm store prune now fails with ERR_PNPM_FROZEN_STORE_WRITE when frozenStore is enabled. It used to remove files from the store.
Store and cache inspection fixes:
pnpm cache list, view, and delete search across registries by default and recognize mixed-case package names. Pass --registry to restrict them to one registry.pnpm cat-file can read executable files from the store.pnpm find-hash reports an unknown hash when the store is empty.--json write errors to stdout.pnpm clean removes custom virtual stores with hidden directory names.pnpm list --lockfile-only --find-by now reads manifests from the configured store when node_modules is absent, and pnpm licenses list reads cached package metadata and license files.
pnpm list --json now reports unsaved dependencies from each workspace project's own modules directory #18248.
pnpm why --exclude-peers now leaves out packages that are reached only as a resolved peer dependency. The flag was accepted but ignored.
pnpm sbom now assigns workspace dependency relationships consistently across runs.
pnpm now fails with ERR_PNPM_CONFIG_UNRESOLVED_ENV_VAR when a setting in pnpm-workspace.yaml or the global config.yaml references an unset or empty environment variable without a fallback. A string setting used to get an empty string in its place #10963.
--config.<name> options now validate their values. --config.storeDir and --config.stateDir work like --store-dir and --state-dir. An empty --state-dir= resets to the default state directory, as --store-dir= does.
noProxy in pnpm-workspace.yaml or the global config.yaml now fails validation unless it is a string or a boolean. null leaves the setting unset.
pnpm doctor checks the resolved global bin directory on PATH.
pnpm --version now succeeds when the project pins another package manager.
Fixed pnpm dropping Ctrl+C just before launching its native binary through Corepack or Node.js on Unix #18222.
The pnpm npm package provides bundled node-gyp to lifecycle scripts even when pnpm's own install scripts were skipped #18227.
The pnpm binary is about 16% smaller on Linux and macOS.
Tab completion suggests project scripts when you type pnpm followed by a script name #18239. Shell completion uses the cursor position when editing an existing command.
The help for pnpm config get and pnpm get now says that the key is a property path, such as catalog.react.
Removed the obsolete xmas command.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
…in pnpm list --recursive . It also includes a security fix. After the default or a scoped registry changed, pnpm install could skip the minimumRelease…
pnpm 12.22.0 adds a globalPackagesConfig section to the global config.yaml for settings that apply only to global packages, adds pnpm why --ranges, and lists workspace projects in dependency order in pnpm list --recursive. It also includes a security fix. After the default or a scoped registry changed, pnpm install could skip the minimumReleaseAge and trustPolicy checks against the new registry.
Settings under globalPackagesConfig in the global config.yaml now apply only to commands that act on global packages, such as pnpm add -g and pnpm update -g. For example, globalPackagesConfig.trustPolicyExclude excludes a package from the trust policy for global installs only #18130.
pnpm approve-builds -g and pnpm add -g --allow-build now save build decisions under globalPackagesConfig.permissions. pnpm still applies build settings from the pnpm-workspace.yaml of the global packages directory, with a deprecation warning. The next approval moves them to config.yaml.
Added pnpm why --ranges, which lists the version range that each direct dependent declares for the package. pnpm why --json now includes the declared range of each dependent in a requires field #18121.
pnpm list --recursive now lists workspace projects in dependency order. Use --no-sort to retain workspace order #7716.
A file: dependency on a local directory now resolves catalog: specifiers in that directory's package.json against the workspace catalogs, as an injected workspace package does. Before, the install failed with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER.
A file: dependency on the publishConfig.directory of a project is now described by that project's package.json, as an injected workspace package is. A package.json that a build writes into that directory no longer changes the resolution.
The experimental v13 lockfile format records a local directory package's declared specifiers in its dependencies and optionalDependencies, beside the versions they resolved to. A dependency marked injected in dependenciesMeta has injected: true. The format no longer has a dependenciesMeta field. Run pnpm install to rewrite a v13 lockfile that an earlier pnpm wrote.
pnpm install now re-verifies lockfile resolutions when the default registry or a scoped registry changes. Before, it reused the result cached for the previous registry and skipped the minimumReleaseAge and trustPolicy checks against the new one #18070.
For a registry with serverType: pnpr, pnpm install also verifies locked package revisions against the registry when no cached result applies.
pnpm dlx no longer reuses a cached install made under looser overrides, packageExtensions, minimumReleaseAge, trustPolicy, trustLockfile, or blockExoticSubdeps settings. It also no longer applies overrides, packageExtensions, or blockExoticSubdeps from a local pnpm-workspace.yaml #18075.
pnpm dlx --allow-build=!<pkg> now denies build scripts for <pkg>, including the executed package itself. Denied packages also skip interactive build approval.
pnpm audit now reports advisories whose id is a string. Such advisories were dropped, and pnpm audit reported no known vulnerabilities #18184.
When the pnpm package downloads its native binary on first run, it now reads a global config.yaml that holds only blank lines or comments as no settings. Such a file made every command fail with "expected a document, but the input is empty" #18172.
When the pnpm package downloads its native binary on first run, it now works with registries that serve no per-version package documents, such as Azure Artifacts. If such a registry also removed npm's signatures, pnpm fetches them from registry.npmjs.org. The binary still comes from the configured registry and is checked against npm's signature.
Fixed an offline install failing the minimumReleaseAge lockfile check with ERR_PNPM_NO_OFFLINE_META after an online install resolved the same packages with the same cache directory. The check now reads publish times from the metadata that the resolution cached #18063.
pnpm install no longer runs git ls-remote for a git dependency whose specifier is unchanged and whose commit the lockfile already records. Installs that update the lockfile, such as Renovate's, no longer fail without git credentials when the project has a private git dependency with peer dependencies #18104.
npm:<pkg>@<range> and named-registry package aliases with space-separated comparators, such as npm:bar@>=1.0.0 <2.0.0, now resolve the target package #18169.
pnpm install with lockfile.format: v13 no longer fails with ERR_PNPM_NEXT_LOCKFILE_NOT_REPRESENTABLE when it converts a v9 lockfile in which a package with many peers has a hashed peer suffix and is in a dependency cycle with one of its peers #18148.
pnpm deploy --prod now succeeds with lockfile.format: v13 when a production package's optional peer is provided only by development dependencies. The excluded provider stays out of the deployed project #18117.
pnpm deploy now preserves lockfile.format and lockfileIncludeTarballUrl in the deployed pnpm-workspace.yaml. Previously, commands such as pnpm dedupe --check in a deployed project using lockfile.format: v13 treated the lockfile as v9 and reported changes.
Fixed pnpm install --merge-git-branch-lockfiles --frozen-lockfile failing with ERR_PNPM_OUTDATED_LOCKFILE when a project sets or removes publishConfig.directory, publishConfig.linkDirectory, or dependenciesMeta. Lockfile merging now preserves and reconciles publishDirectory, linkDirectory, and dependenciesMeta on importers.
Frozen installs accept injected workspace packages whose child dependencies use link: or a bare relative path pnpm/tasks#274.
Installing an injected local package no longer fails with a "no such file or directory" error when another process renames or removes files in that package while pnpm lists them. This happened most often on macOS in workspaces with sharedWorkspaceLockfile: false, where the install of the package itself writes its lockfile at the same time.
Fixed a crash when pnpm-lock.yaml or a dependency selector contains a package name that starts with a multi-byte UTF-8 character.
Tarball URLs that reject HEAD requests with 405 Method Not Allowed now fall back to a GET request during resolution.
With autoInstallPeers, an optional peer is no longer bound to a version outside its range that only another dependency's subtree brings in. Before, adding an unrelated dependency could flip that binding and rewrite the peer suffixes of other projects in the lockfile #18162.
Fixed duplicate packages with nodeLinker: hoisted and autoInstallPeers: false when identical transitive peer bindings appeared under parents with conflicting dependencies.
When multiple overrides selectors match a dependency, pnpm now picks the selector with the narrower version range regardless of the order in which the overrides are declared #18071.
Patches that add lines to the end of a file without a final newline now install the whole file. pnpm dropped the last added line when the patch also marked it with \ No newline at end of file #18156.
Project engines.node checks now use the Node.js runtime that pnpm links for the dependency groups being installed. If the lockfile records that runtime, the check uses its resolved version. Production installs ignore a runtime declared only in devEngines.runtime pnpm/tasks#302.
pnpm install and pnpm approve now discover, link, and prune agent skills from workspace:*, link:, and local directory file: direct dependencies.
pnpm add crate: and targeted pnpm update crate: commands keep compatible versions from Cargo.lock for other crates pnpm/tasks#257.
pnpm add crate:<pkg> no longer corrupts multiline arrays in Cargo.toml. Saving an explicit version with pnpm add crate:<pkg>@<version> now replaces workspace = true on existing dependency entries. Inherited workspace settings such as features, default-features, and package stay on the updated entry. pnpm install now accepts unversioned path dependencies on prerelease Cargo workspace members. Cargo workspace inheritance now resolves package renames.
pnpm add for pypi: dependencies now preserves existing entries in pyproject.toml whose PEP 508 environment markers differ from the added requirement. pnpm add also accepts PEP 508 direct URL requirements such as pypi:pkg @ https://.... pnpm update at a shared-environment workspace root without a root [project] table now updates matching member manifests and the shared pylock.toml.
An invalid entry in a Python registry's packages list now names the patterns a Python registry accepts: an exact name, a prefix such as company-*, or **. The error used to suggest @scope/*, which a Python registry rejects. It also quotes the entry as written. A rejected prefix such as -a* used to appear as -ax.
verifyDepsBeforeRun no longer reports the dependencies as out of date when runtimeOnFail stops pnpm from installing the runtime that devEngines.runtime or engines.runtime declares #18155.
Commands that install a single project of a workspace, such as pnpm add -w, now apply runtimeOnFail to the other workspace projects too. They no longer install a runtime that runtimeOnFail excludes.
pnpm --if-present start, pnpm run --if-present start, and pnpm restart --if-present now exit with code 0 when a project has neither a start script nor a server.js file #18073.
pnpm test, pnpm t, and pnpm tst in a single-package project now fail with ERR_PNPM_NO_SCRIPT when the test script is missing unless --if-present is passed #18073.
shellEmulator now handles escaped backslashes (\\) and unquoted escaped single quotes (\') according to POSIX quoting rules. Previously, scripts containing "a\\" or \' failed to parse or misquoted later ${...} parameter expansions.
pnpm create now forwards --env-file and other CLI flags placed after the starter template name to the starter command.
pnpm pipeline now hashes no input files when inputs: [] is configured. +-prefixed input globs include gitignored files and workspace files outside the project directory. !-prefixed input globs exclude matching files. Tasks that depend on an uncacheable task now bypass cached output restoration and re-run after that dependency executes. Read-only cached output files restore without permission errors. Task keys now hash each project's wanted lockfile across per-project lockfiles, custom lockfileDir, and branch lockfiles.
pnpm approve-builds and pnpm approve without package arguments or --all now fail with ERR_PNPM_APPROVE_BUILDS_NON_INTERACTIVE and ERR_PNPM_APPROVE_NON_INTERACTIVE when packages are awaiting approval in CI or without an interactive terminal. pnpm dlx and global installs also skip automatic build-approval prompts in CI, leaving pending builds unapproved.
pnpm approve-builds and pnpm add --allow-build no longer corrupt a pnpm-workspace.yaml whose last line has no line break.
Combining --filter and --filter-prod with exclusion selectors such as !pkg now evaluates all selectors together in command-line order. An exclusion passed on one flag while inclusions were passed on the other no longer selects every workspace project.
pnpm -r fetch now fetches each selected project's lockfile when sharedWorkspaceLockfile is false. Use --filter to limit which projects are fetched #18152.
pnpm peers in workspaces with sharedWorkspaceLockfile: false now checks each selected project's pnpm-lock.yaml.
pnpm ci now validates that pnpm-lock.yaml exists and matches package.json before removing node_modules. pnpm clean and pnpm ci now honor --filter, --filter-prod, and --workspace-root. pnpm clean and pnpm ci also clean root node_modules in workspaces without a root package.json. pnpm clean --lockfile now removes per-project lockfiles and lockfiles inside a custom lockfileDir.
pnpm clean, pnpm purge, and pnpm ci keep files outside the project untouched when modulesDir points outside the project root. When node_modules is a symlink, pnpm now unlinks the symlink without modifying its target #18072.
pnpm import now preserves locked versions for npm: aliased dependencies when importing from package-lock.json, npm-shrinkwrap.json, or yarn.lock. pnpm import also parses Yarn Classic yarn.lock files that reference __metadata package names without treating them as Yarn Berry lockfiles.
pnpm update now moves an engines.pnpm range along with the pnpm version in packageManager or devEngines.packageManager #18142.
Fixed GitHub Actions support in pnpm update and pnpm outdated. Updating a workflow step with a major or minor version comment such as # v4 or a prose comment now formats the updated version comment cleanly. Negated action selectors such as !actions/cache/save now exclude only the targeted subpath actions. Passing only negated action selectors still updates packages. Previously, negated action selectors skipped package updates. pnpm outdated now reports every distinct outdated version when several workflows pin the same action at different versions.
Fixed pnpm update skipping package updates when a Package URL selector such as pkg:npm/foo is combined with --include-github-actions.
pnpm update -g --latest now upgrades global runtimes (node, deno, and bun) and npm:-aliased global packages across major versions.
pnpm update --changeset now generates a changeset when a .changeset directory exists or versioning is configured in pnpm-workspace.yaml, without requiring .changeset/config.json. It also respects versioning.ignore alongside .changeset/config.json.
pnpm version -r now runs each bumped package's preversion, version, and postversion scripts unless --ignore-scripts or --dry-run is set. pnpm version -r --dry-run --json now prints the planned releases as a JSON array.
pnpm lane <lane> --filter <selector> now rejects partial moves of a versioning.fixed group with ERR_PNPM_VERSIONING_CONFLICTING_CONFIG before writing pnpm-workspace.yaml.
pnpm -C <dir> publish <tarball|folder> and pnpm --dir <dir> publish <tarball|folder> now resolve relative tarball and directory arguments against <dir>. Git checks during pnpm publish also inspect the target directory.
pnpm -r publish now skips workspace manifests whose name or version field is an empty string.
pnpm -r pack --out now expands %s and %v placeholders only in the --out template. Literal %s and %v segments in the working directory path stay unchanged.
pnpm config set --global --json tools now writes tools to the global config.yaml and validates its structure before saving. pnpm config set --global also accepts pm-on-fail and runtime-on-fail. blockExoticSubdeps and excludeLinksFromLockfile set in the global config.yaml now take effect during installs and appear in pnpm config get --global. pnpm now ignores workspace-only settings in the global config.yaml and prints a warning, matching pnpm config set --global.
${VAR} placeholders in pnpm-workspace.yaml written with YAML flow syntax now fail on registry URLs with ERR_PNPM_REGISTRY_ENV_NOT_EXPANDED. Placeholders in flow-style proxy, pnprServer, and userAgent settings are now ignored with a warning #18074.
updateConfig and afterAllResolved hooks in .pnpmfile.cjs that return undefined, null, or a non-object value now fail with ERR_PNPM_CONFIG_IS_UNDEFINED and ERR_PNPM_BAD_AFTER_ALL_RESOLVED_RETURN.
finders in .pnpmfile.cjs that return an empty string no longer match packages in pnpm list --find-by or pnpm why --find-by.
pnpm list no longer adds an npm: prefix to aliased local file: directory dependencies, and pnpm list --json preserves <name>@file:<path> in their version field.
pnpm list --parseable --long now keeps <name>@ on link: and file: dependencies whose path or peer suffix contains @, such as link:../@scope/pkg. Aliased scoped file: dependencies whose path contains @ also keep <name>@ in pnpm list.
pnpm why no longer merges distinct local file: directory dependencies that share the same package name across projects with dedicated lockfiles (sharedWorkspaceLockfile: false).
pnpm sbom and pnpm licenses list now resolve namedRegistries version prefixes in lockfile entries. pnpm sbom emits bare component versions with a sanitized repository_url PURL qualifier. pnpm sbom derives tarball download URLs from the named registry. pnpm licenses list reports packages from named registries as separate entries with bare versions and registryName.
pnpm pkg now reads and writes the project manifest as written on disk. pnpm pkg get no longer reports synthetic runtime: dependency entries from devEngines.runtime or engines.runtime. pnpm pkg set and pnpm pkg delete now preserve devEngines.runtime, engines.runtime, and empty dependency objects set with --json.
pnpm pm now works after CLI flags such as --dir and after pnpm with current. pnpm with current also accepts subcommand boolean flags such as pnpm --bare with current init ahead of with.
pnpm env commands (use, list, and remove) now accept Node.js version specifiers with a leading v, including prerelease versions such as v22.0.0-rc.1.
pnpm doctor now checks write access for the cache, store, and global bin directories before they have been created. Previously, pnpm doctor reported no write access on fresh environments.
pnpm doctor now probes whether reflinks or hardlinks work from the store into the project's link target and warns when neither does.
An error from a failed dependency resolution, such as an unreachable registry or a throwing pnpmfile resolver, now prints its cause once #18077.
pnpm no longer wraps error messages at the output width, so URLs and paths in them stay intact when stderr is not a terminal #18078.
pnpm install with nodeLinker: hoisted no longer counts missing packages as removed. This fixes inflated removal counts for skipped optional dependencies #18178.
pnpm outdated --json and pnpm outdated --format=json now write reporter warnings to stderr. Warnings previously appeared on stdout before the JSON output.
pnpm stage with --json now keeps stdout valid JSON during dry runs, empty workspace runs, and errors. pnpm pipeline --dry-run --json and pnpm -r run --dry-run --json now write reporter warnings and scope lines to stderr.
pnpm warns when an updateConfig hook changes registries and some routes still use their configured registry. The warning names those routes and points to registriesByScope.
pnpm cat-file now reports ERR_PNPM_INVALID_HASH when given an empty, malformed, or truncated digest such as sha512-.
pnpm 12.21.0 lets pnpm store add prepare tarball and git dependencies for offline installs. It also makes repeated installs keep their peer dependency
pnpm 12.21.0 lets pnpm store add prepare tarball and git dependencies for offline installs. It also makes repeated installs keep their peer dependency choices and fixes several lockfile.format: v13, nodeLinker: hoisted, and pnpm deploy failures. If a pnpr server refuses a setting, pnpm now resolves locally.
pnpm store add run in a project now prepares downloaded tarballs for every lockfile entry that pins them. Besides registry packages, pnpm install --offline --frozen-lockfile can then install dependencies on a tarball URL and dependencies on a git host such as GitHub whose lockfile entry records an integrity.pnpm now reads a lockfile with a mapping key longer than 1,024 characters written as 'key':, without the ? marker. Before, pnpm install and other commands failed on such a lockfile with ERR_PNPM_BROKEN_LOCKFILE.
With lockfile.format: v13, pnpm install no longer fails to create or rewrite the lockfile when a package declares many of its dependencies as peers.
Fixed pnpm deploy failing with lockfile.format: v13 when injected workspace packages have hashed peer bindings.
Frozen installs with v13 lockfiles now accept valid peer dependencies of injected workspace packages that use catalogs.
Fixed injected workspace packages that depend on themselves linking to a nonexistent directory.
pnpm install with frozenStore enabled no longer fails with ERR_PNPM_FROZEN_STORE_NEEDS_BUILD when nodeLinker is hoisted. pnpm fetch with nodeLinker: hoisted no longer populates global virtual store links or modifies linked agent skills, and it preserves an existing hoisted node_modules directory #18037.
A requirements.txt beside a pyproject.toml that declares [tool.uv.workspace] without a [project] table no longer makes that directory a Python project. pnpm install stopped there with an error when the directory had a .venv that pnpm did not create #18023.
Repeated installs no longer change the peer dependency providers that the previous install chose. This covers adding, updating, or removing a dependency, projects that use different ranges of one dependency, dependency cycles, and injected dependencies with autoInstallPeers: false pnpm/tasks#221.
An unchanged install keeps a valid locked peer provider even when a direct dependency provides another compatible version. Explicit pnpm add and pnpm update requests take precedence over it.
Workspace projects that select different versions of a peer provider no longer share one copy of the package that depends on it. This affected peers reached through an aliased dependency or a peer dependency cycle.
A removed dependency no longer comes back as a peer provider. Before, a direct dependency removed with autoInstallPeers: false could be restored from an old peer resolution, and a removed one could still supply its old peer context.
With nodeLinker: hoisted and autoInstallPeers: false, pnpm install no longer creates duplicate copies of a package whose resolved peers are identical. A package also no longer loads a copy of its dependency that was resolved with different peer versions #18003.
pnpm deploy now binds optional peers declared only in peerDependenciesMeta for linked workspace packages. The deployed manifest and lockfile also retain these peers when filtering dependency groups.
Scripts now stop when pnpm's process group is killed while they are starting.
Bin shims in the global virtual store no longer include the hoisted modules directory of the project that installed them #18035.
pnpm pipeline now rebuilds local packages and reruns build scripts after it restores a shared Cargo build cache with Cargo 1.100 or newer. Before, a worktree could reuse build-script output from the worktree that created the cache.
If the pnpr server refuses a setting the install uses, or cannot return the lockfile format pnpm reads, pnpm install and pnpm update print a warning and resolve locally. Cargo and Python resolution also fall back to resolving locally. pnpm now rejects a pnpr resolution of npm dependencies that does not name its lockfile format.
pnpm install with pnprServer now limits the size of the server's resolve and lockfile verification responses. An oversized response ends the request with an error.
pnpm now displays pnpr error codes and reasons when remote requests fail.
pnpm setup and the install script now support PowerShell as the login shell on Linux and macOS. They add PNPM_HOME to PATH in profile.ps1 under $XDG_CONFIG_HOME/powershell or ~/.config/powershell #18026.
A lockfileDir setting that points at the default lockfile directory now installs the same way as leaving it unset pnpm/tasks#275.
The node-gyp bundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947 . On Node.js 26, node-gyp downloads through a…
pnpm 12.20.0 records the specifiers of local directory dependencies in the experimental v13 lockfile and fixes several nodeLinker: hoisted, peer dependency, and overrides bugs. The bundled node-gyp no longer ships the undici version that security scanners flag. Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older.
lockfile.format: v13, pnpm install records the dependency specifiers of local directory packages. Frozen installs reject changed specifiers even when the locked versions still satisfy them.Remote resolution, shared build caches, and release notes no longer work with pnpr 0.1.0-alpha.19 or older. pnpm now reads the capabilities a pnpr server advertises under pnpr.protocols. Installs fail when the server does not confirm the requested resolution and verification policies.
The node-gyp bundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947. On Node.js 26, node-gyp downloads through a proxy or with a custom CA file no longer crash with "invalid onError method" #17941.
Version-selector overrides entries such as "ms@^2.0.0": "2.1.1" now apply to dependencies declared with the catalog: protocol when the catalog entry's range matches the selector #17922.
A root overrides entry that points a package at a workspace: path, such as workspace:./packages/foo, now also applies when a registry package depends on that package pnpm/tasks#270.
Git dependencies now accept npm's :: separator between fragment parameters, such as github:owner/repo#v1.0.0::path:packages/foo. Before, pnpm read the whole fragment as a branch name and failed to resolve it #17827.
pnpm dedupe now keeps a locked runtime version, from devEngines.runtime or from a dependency's engines.runtime, when the declared range still admits it. pnpm dedupe --check no longer fails each time a newer Node.js release in the range comes out #17984.
With autoInstallPeersFromHighestMatch, conflicting non-semver peer dependencies now remain missing, and identical non-semver peer specifiers are preserved. Preferred registry versions no longer replace local paths or protocol-prefixed specifiers when pnpm installs missing peers pnpm/tasks#272.
nodeLinker: hoisted, a package now keeps its nested copy of a dependency that it resolved at a version other than the top-level one, including a peer dependency its parent supplies. Before, pnpm could remove that copy as a duplicate or give the top-level slot to a peer variant found deeper in the graph. The package then loaded the top-level version.Fixed pnpm install keeping stale peer bindings after dependency changes. Required dependencies no longer remain marked optional when another workspace project removes a shared package pnpm/tasks#221.
Repeated installs now keep the same dependency links when packages form cycles with several peer dependency variants pnpm/tasks#221.
Fixed writing lockfile.format: v13 for dependency cycles with missing, optional, or transitive peers. Frozen installs also accept unchanged injected packages whose peers use catalogs. With --no-optional, frozen installs reject required catalog children recorded only as optional dependencies pnpm/tasks#221.
pnpm deploy preserves an injected workspace package's resolved dependencies when they differ from the workspace project's own dependencies. This also applies to packages with publishConfig.directory pnpm/tasks#221.
Scripts that pnpm runs in a process group of their own are now ended when pnpm is killed right after starting them. A parallel run that was killed before pnpm registered its scripts left all of them running.
When a command name matches no script and pnpm falls back to running it as a command, the install that runs before scripts now runs once. Its errors and warnings print once #17977.
Failed downloads by project-aware global runtime commands now explain which configuration applies. Node.js failures also list the global mirror settings and environment variables to check.
Fixed pnpm occasionally crashing on the first HTTPS request, mostly on Windows virtual machines under load. pnpm now seeds TLS randomness from the operating system's random number generator pnpm/tasks#239.
Fixed pnpm deprecate, pnpm undeprecate, and pnpm unpublish failing with revision conflicts when a registry cache serves stale package metadata.
pnpm sbom now reports malformed workspace manifests. Before, it omitted their packages pnpm/tasks#59.
Fixed pnpm store status reporting approved builds of git dependencies as modified when the store contains legacy build metadata.
pnpm now recognizes Capawesome Cloud and RWX as CI environments.
…JSON lockfile format. It also includes a security fix: an offline install error no longer prints registry credentials. pnpm now checks the engines and…
pnpm 12.19.0 adds pnpm fund, lets the loaded node linker handle packages that need a build, and adds the projectScopedOptionalPeers setting and an experimental JSON lockfile format. It also includes a security fix: an offline install error no longer prints registry credentials. pnpm now checks the engines and platform fields of every workspace project, and many hoisted-linker and frozen-lockfile bugs are fixed.
Added pnpm fund, which lists the funding URLs declared by the installed dependencies in the same tree npm fund prints. Use --json for the npm fund --json report and --recursive or --filter to report on workspace projects. pnpm fund <pkg> opens the funding URL of an installed package, and --which picks one when it lists several #7354.
With nodeLinker.type: loaded, packages that need a build no longer have to be listed in nodeLinker.excluded. A package with a matching side-effects cache entry loads from the store. If side-effects cache reads and writes are enabled, pnpm builds an approved package once, saves the result to the side-effects cache, and then loads it from the store. This includes a build that changes no files in its package, so its script does not run again in other projects that use the same store. List a package in sideEffectsCache.exclude if its build must run in every project, such as a git hook installer. pnpm materializes other cache misses, packages with native .node addons, and their dependencies automatically.
pnpm also scans JavaScript sources for filesystem imports and for __dirname or import.meta, and materializes matching packages. The scan does not detect computed imports. List such packages in nodeLinker.excluded.
Added the projectScopedOptionalPeers setting. When it is true, a project gets a missing optional peer dependency only if the project's own dependencies install a version of it. Another workspace project's dependencies, such as its devDependencies, no longer supply one. dedupePeerDependents keeps deduplicating everything else #16666.
Added the experimental lockfile.format: v13 setting. With it, pnpm writes pnpm-lock.yaml in a JSON-like syntax, indented with tabs, with a trailing comma after every entry. The file is still valid YAML. The file has one packages entry per package version in place of the packages and snapshots sections, and each entry records the versions of its peer dependencies as its properties. Updating a peer dependency then changes only the lines that record its version. pnpm reads lockfiles in both formats whatever the setting is.
pnpm store add now accepts directories of tarballs, such as pnpm store add ./tarballs, and adds every .tgz, .tar.gz, and .tar file inside them recursively. pnpm store add is now faster when it adds many packages or local tarballs #17875.
With supportedArchitectures set, pnpm install and pnpm fetch also store, without linking them, the dependencies of the archives kept for the other listed platforms. A platform added to the setting gets its archives and their dependencies on the next install. Optional dependencies a listed platform cannot run are not stored, and one that fails to download is skipped. Dependencies from git repositories are not stored for other platforms.
When supportedArchitectures names exactly one platform and not current, pnpm links that platform's variant of a package published with platform variants, together with that variant's dependencies. This holds for the list form and for the os, cpu, and libc form. A variant whose floor or ABI the listed platform does not state is not linked for it: pnpm links another variant that fits, or the version's own archive. Changing the setting, or the platform of the host, such as a node_modules mounted into a musl container or a Node.js with another ABI, relinks the package on the next install, even from a frozen lockfile.
pnpm now provides a prebuilt binary for NetBSD 10 on x64 #17803.
pnpm install, pnpm ci, and pnpm install-test outside a workspace now fail with ERR_PNPM_NO_PKG_MANIFEST when the directory has no package.json, package.json5, or package.yaml. They no longer create a package.json, a lockfile, and node_modules there #17727.
Fixed pnpm install hanging when a concurrent tarball download or manifest read is cancelled while other tasks are waiting on the same archive.
Running a global command such as node in a project that pins its version no longer hangs while pnpm installs that version. The hang kept starting new processes until the machine ran out of memory.
A global command such as node now runs the version a project pins when PNPM_CONFIG_LOCKFILE_DIR, PNPM_CONFIG_VIRTUAL_STORE_ONLY, or PNPM_CONFIG_SYMLINK is set in the environment. Before, the dispatch failed with "the installed node executable is not under" the store.
pnpm install now fetches fresh metadata for a package when a version allowed by minimumReleaseAgeExclude is missing from the cached metadata. Before, it could fail with ERR_PNPM_NO_MATCHING_VERSION without contacting the registry #17723.
A ${VAR} placeholder in a registry URL in pnpm-workspace.yaml or the project .npmrc now fails the command. pnpm does not expand environment variables in these files. Before, pnpm ignored such a URL and resolved packages from another registry, such as npmjs.org. pnpm now warns when it ignores a placeholder in a proxy, pnprServer, or userAgent setting in pnpm-workspace.yaml #17762.
Fixed local package installs failing while a workspace lockfile is being written.
pnpm self-update and switching to the packageManager version now work behind a proxy that ends a response by closing the TLS connection without a close_notify alert. The registry signature check failed there with ERR_PNPM_PNPM_ENGINE_IDENTITY_UNVERIFIABLE #17763.
A package tarball that keeps failing to download now fails the install after fetchRetries retries. pnpm used to download it again with a second full set of retries, which doubled the wait. The error now names the actual download failure.
When the native binary of the pnpm version a project pins fails to download, pnpm now reports the download error. It used to report only that no native binary was found for the host.
POSIX bin shims and the pnpm, pn, pnpx, and pnx launchers now run inside a Nix build on macOS with the sandbox enabled. Installing again replaces the shims already in node_modules #17750.
Fixed pnpm leaving process pipes open after it exits on macOS pnpm/tasks#229.
pnpm install, pnpm add, pnpm update, and pnpm remove now check the engines, os, cpu, and libc fields of every workspace project, including the workspace root. pnpm run -r and pnpm exec -r check them before running anything. An incompatible engines.pnpm fails the command. An incompatible engines.node prints a warning, or fails the command with engineStrict enabled. An unsupported platform prints a warning. A project that downloads its own Node.js through devEngines.runtime is checked against that Node.js #17751 pnpm/tasks#281 pnpm/tasks#299.
Fixed missing warnings when a required dependency does not support the current Node.js version.
An optional dependency that declares no os, cpu, or libc field is no longer skipped because its name contains only an operating system word, such as get-windows on macOS. pnpm now infers its platform from the name only when the name also has a cpu or libc token, such as -win32-x64 #17774.
With dedupePeerDependents: false, a missing optional peer is no longer resolved from a version that only another workspace project depends on. The workspace root's dependencies still count if resolvePeersFromWorkspaceRoot is true. Before, a tool in one project's devDependencies, such as webpack-cli, could become an optional peer of another project's production dependencies #16666.
pnpm install no longer gives a project an optional peer dependency that it skipped because a required peer would conflict with the project's dependencies. Before, dedupePeerDependents merged the project's copy of the package that declares the peer with another project's copy that resolves it #17781.
pnpm install no longer fills in a missing optional peer dependency if a required peer it brings in conflicts with a version the project depends on. Before, such a peer was installed along with it and reported as unmet #17718.
pnpm install --filter in a sparse checkout now counts the dependencies of workspace projects that are missing from disk when it resolves peer dependencies and marks packages as optional. The lockfile it writes no longer differs from a full checkout in those entries #17791.
pnpm install --frozen-lockfile now succeeds when a workspace project recorded in pnpm-lock.yaml has an empty directory, such as a git submodule that was not checked out #17712.
pnpm install --frozen-lockfile now fails with ERR_PNPM_OUTDATED_LOCKFILE when a workspace package linked through a plain semver range, such as ^7.9.5, has changed to a version outside that range #17806.
pnpm install --frozen-lockfile and verifyDepsBeforeRun now accept a workspace: dependency on a project whose version is not valid semver, such as workspace:1 on a project at version 1. Before, they reported the lockfile that pnpm install had just written as out of date.
pnpm install --frozen-lockfile now accepts a lockfile when an injected workspace package declares a file: or link: dependency with backslashes, such as file:..\vendor, or with a slash after the protocol, such as file:/./vendor. Before, the install reported the lockfile as out of date right after pnpm install had written it #17720.
When a package injected through a path, such as file:../lib or ../lib, gives one of its dependencies a catalog: specifier, pnpm install --frozen-lockfile now reports the lockfile as outdated. For a bare path such as ../lib, pnpm install now also fails the way a fresh resolution does. Before, these installs accepted the existing lockfile #17722.
Dependencies declared as workspace: entries in catalogs now remain in the lockfile when excludeLinksFromLockfile is enabled. Frozen installs can restore these links after node_modules is removed pnpm/tasks#260.
With dedupeDirectDeps, pnpm install now compares link: dependencies by the directory they point at. A project's link: dependency is removed when the workspace root links the same directory under a different path. It is kept when the root's link: dependency has the same text but points at another directory. pnpm reports a dependency the root provides as removed only once, when it removes the project's link. The summary shows the package version of a removed link: dependency pnpm/tasks#293.
With nodeLinker: hoisted, a package that runs a lifecycle script or has a patch is now cloned or copied into node_modules, as with the isolated linker. A build that rewrites one of its files no longer changes the store copy shared with other projects.
With nodeLinker: hoisted, pnpm no longer deletes a directory outside node_modules when it removes a package whose scope directory is a symlink.
With nodeLinker: hoisted, pnpm install --filter in a sparse checkout now drops previously installed workspace projects that are missing from disk from the hoisted node_modules tree. It no longer recreates node_modules inside a missing project's directory. Packages that only the missing project used are also removed from the root node_modules.
With nodeLinker: hoisted and dedupeDirectDeps, pnpm install now removes a project's link: dependency that the workspace root provides, and reports each link: dependency it removes. Removing the last scoped link: dependency of a scope also removes the empty @scope directory.
With nodeLinker: hoisted and a custom modulesDir, pnpm now installs a workspace project's dependencies that cannot be hoisted to the root into the project's modulesDir. The next install that relinks the project removes the copies that earlier installs left in its node_modules. A later install restores the project's modulesDir when it was removed. Package directories that pnpm did not install are now also moved to .ignored in a custom modulesDir.
Fixed installs in a workspace whose modulesDir is an absolute path, including one that goes through a symlink such as /tmp on macOS, or a path that starts with ... Dependencies of workspace projects no longer end up outside the workspace, and the root project's dependencies, link: dependencies, and commands are linked into the configured directory. pnpm bin, pnpm root, pnpm run, pnpm exec, and pnpm version now use that directory too pnpm/tasks#285.
Concurrent installs into a global virtual store no longer wait on each other. A package that needs a build is built in a private directory and moved into the store once its build has finished, so another project never links a half-built package. An install with --ignore-scripts links the packages it does not build from their own store directories, and pnpm store prune removes the build directories of installs that were interrupted #15568.
Packages that an older pnpm version added to the store now run their install scripts. Before, pnpm could skip those scripts and hardlink the package's files to the store.
pnpm install now keeps patches to bundled dependencies when it restores a package from the side-effects cache, including files a patch adds #17734.
Local installs on macOS now keep cached clones separate from the global virtual store. pnpm store prune removes this cache, so unused cached packages no longer accumulate #17907.
pnpm store prune now stops if a dependency link cannot be read. This keeps installed packages from being removed after an incomplete scan.
A repeat pnpm install now runs a full install when the runtimeOnFail setting changes. Before, it printed "Already up to date" and did not install the runtime a project declares in devEngines.runtime pnpm/tasks#303.
The sync of an injected workspace dependency now copies a file whose source has reached the filesystem's limit on hard links. pnpm patch-commit now copies a file into its scratch directory when the filesystem refuses to hard link it, unless the path is missing or already occupied pnpm/tasks#283.
pnpm install is faster when it clones files from the store, which it does by default on macOS. On a Mac with endpoint security software, a cold install of a project with about 1,350 packages took 29% less time pnpm/tasks#280.
pnpm install unpacks packages that contain many files faster. Unpacking typescript took 30% less time in our measurements pnpm/tasks#288.
Resolving against a registry that sends Cache-Control: no-cache, such as Azure Artifacts, is fast again when the lockfile already decides the version. pnpm reads the cached metadata for a pinned version, or for a range the lockfile version is proven to win, without a registry request #17758.
POSIX bin shims start fewer processes. Running a dependency's bin through its shim from Git Bash on Windows starts 7 processes where it started 15. Installing again replaces the shims already in node_modules.
pnpm now installs dependencies and runs lifecycle scripts from projects on mapped Windows network drives. When a network share refuses the links in node_modules, the error now suggests setting nodeLinker: hoisted or moving the project to a local drive #17747.
packageImportMethod: auto now tries hardlinking before cloning, as it does on Linux. Installs from a warm store on a Dev Drive are faster. An install no longer fails when the store refuses a hardlink with an access-denied error, and pnpm tries cloning or copying the file next #17809.
pnpm run and pnpm setup no longer clear the visible terminal when a project path contains non-ASCII characters.
A failed attempt to create a directory junction in node_modules no longer leaves a .pnpm-junction-* directory behind.
pnpm starts faster. It loads system libraries such as user32.dll and shell32.dll the first time a command uses them, so pnpm --version loads 11 libraries where it loaded 25.
pnpm deploy now runs the build scripts of a workspace project that it installs as a file: dependency, without a machine-specific allowBuilds key. An allowBuilds entry that denies the project still applies #17740.
pnpm deploy no longer fails when the deployed project depends on a workspace package that sets publishConfig.directory. pnpm installs that package from its publish directory and runs its build scripts #17771.
pnpm deploy without a shared workspace lockfile now resolves a relative workspace: path, such as workspace:../lib, from the source project's directory. It used to be resolved from the deploy target and fail #17804.
pnpm deploy --offline --trust-lockfile now reuses dependencies pinned in the source lockfile from a populated store when registry metadata is unavailable. This works with per-project lockfiles, --legacy, and npm aliases #17888.
pnpm dist-tag and pnpm unpublish now offer browser-based authentication when the account's two-factor authentication uses a security key. Before, they asked for a one-time password in that case #17832.
pnpm publish with provenance now downloads Sigstore's current signing configuration before signing. A failed or slow download is retried with the same retry policy and deadline as the signing requests.
pnpm pack and pnpm publish now apply the first rule of a .npmignore or .gitignore that starts with a UTF-8 BOM.
pnpm outdated now checks dependencies when the project has no lockfile, for example with lockfile: false. The Current column shows the installed version, or the lowest version allowed by the declared range if the dependency is not installed #17811.
pnpm self-update now updates the project's engines.pnpm range along with its pnpm pin, keeping the ^ or ~ operator #17732.
On Linux and macOS, pnpm run no longer sometimes reports a lifecycle failure after Ctrl+C interrupts a script.
Config dependencies use the declared registry serverType when recording and installing packages pnpm/tasks#236.
Relative directory selectors set on config.filter or config.filterProd by an updateConfig hook now resolve from the workspace root even when --dir is passed or pnpm runs from a subdirectory #17906.
Commands that add settings to pnpm-workspace.yaml now fail with an error if the file contains only null, and leave the file unchanged. Before, they wrote invalid YAML.
Shell tab-completion now completes directory and file paths for path options such as -C, --dir, --prefix, --store-dir, and --env-file. Before, options without a fixed list of values offered command names #17884.
pnpm 12.18.0 packs, publishes, and installs packages with platform variants on pnpr registries. It also adds per-skill approval of agent skills and pn
pnpm 12.18.0 packs, publishes, and installs packages with platform variants on pnpr registries. It also adds per-skill approval of agent skills and pnpm store add for offline installs from downloaded tarballs. Repeat installs and verifyDepsBeforeRun no longer read the package.json of unchanged workspace projects. The release fixes several peer dependency resolution bugs too.
pnpm now names the link to a dependency's agent skill after the skill alone. A skill that the @acme/kit package ships in skills/auth/ is linked as .claude/skills/auth, not .claude/skills/pnpm-@acme+kit-auth. The next install replaces links with the old names. pnpm lists the linked skills in a # pnpm block of each agent skill directory's .gitignore #17455.
When two approved packages ship a skill of the same name, or the name is already taken in an agent skill directory, pnpm links the skill as pnpm-<package>-<skill>. Before, the install failed.
pnpm approve now asks which agent skills to link when a package ships more than one. pnpm records the chosen skills as a list, such as permissions.<pkg>.skills: [guide, migrate], and does not offer the other skills for approval again. The first time a project approves a skill, pnpm approve also asks which agent directories to link skills into, and records the answer under skills.dirs.
pnpm links agent skills nested in category directories, such as skills/engineering/implement/SKILL.md, up to three levels below skills/. Before, it linked only the skills directly under skills/.
These features need a registry declared with serverType: pnpr.
pnpm pack packs one archive per entry of publishConfig.variants, each platform variant as <name>-<version>~<tag>.tgz. pnpm pack --variant <target> packs only the archive whose entry lists that target. pnpm pack --json prints the integrity and size of every archive it writes.
pnpm publish publishes a package's publishConfig.variants. pnpm uploads every archive before the publish request that references them. Publishing variants to any other registry is refused unless --no-variants is given, which publishes only the archive that targets any.
pnpm publish --upload-variant <target> uploads the archive of one publishConfig.variants entry to the registry's staging area and prints <target>=<integrity>. pnpm publish --variant-integrity <target>=<integrity> then publishes the version from archives that other jobs uploaded. With --recursive, each value names its package as <name>~<target>=<integrity>.
pnpm publish -r --batch now uploads each package archive on its own request and skips archives the registry already holds, so the batch request no longer grows with the archives it publishes. A batch of more than 256 packages still carries every archive inline. Packages with publishConfig.variants can be published in a batch. A batch with variants that would reference more than 256 archives on one registry fails with ERR_PNPM_BATCH_PUBLISH_TOO_MANY_ARCHIVES pnpm/tasks#244.
pnpm publish --provenance signs one statement that names every archive of a version with publishConfig.variants. A platform variant's archive is named by the version's package URL with a variant qualifier.
Rerunning pnpm publish after the version was already published now succeeds when the published version is the same release. pnpm compares the archives, the provenance statement when the rerun signs one, and the dist-tag. When the published version differs, the publish fails with ERR_PNPM_PUBLISHED_RELEASE_DIFFERS, which names what differs.
pnpm installs the platform variant of a package that fits the host, or the package's own archive when none does. The lockfile records every variant. A version published with variants only, and no archive for other hosts, installs on a host one of the variants fits. On any other host, an optional dependency is skipped, and any other dependency fails with an error that lists the platforms the version is published for.
supportedArchitectures platform lists accept platform tags, the same tags publishConfig.variants entries name. An entry can state floors and an ABI, such as linux-x64-manylinux_2_28, darwin-arm64-macos_14_0, linux-x64-napi8 or linux-x64-node127, and any Node.js OS and CPU, such as freebsd-x64. The spellings accepted before still work.
With supportedArchitectures set, pnpm also fetches into the store the variants that the other listed platforms need, when it downloads a package with platform variants.
pnpm downloads less metadata from a registry declared with serverType: pnpr. A large package document leaves out the manifests of rarely picked versions, and pnpm fetches one only when it picks that version. In a benchmark that resolves 787 packages, the package documents shrank from 30.3 MB to 2.5 MB gzipped. pnpm caches these documents in v12/metadata-pnpr, and the pnpm cache commands cover them.
pnpm warns when a registry that is not declared serverType: pnpr turns out to be pnpr. For a registry declared serverType: pnpr, a minimumReleaseAge longer than 30 days fails with ERR_PNPM_UNSUPPORTED_MINIMUM_RELEASE_AGE.
pnpm publish sends release notes to registries declared with serverType: pnpr. A package's notes are the section for its version in CHANGELOG.md, or the notes that pnpm version -r composed from change intents. --release-notes <file> gives the notes from a file, and --no-release-notes sends none. --publication-name names a release published with --batch.
In a workspace that uses pnpm's versioning, pnpm version -r --release-notes <file> puts a summary above the composed notes of the release.
pnpm view <pkg>@<version> releaseNotes, pnpm outdated --notes, and pnpm update --interactive show the release notes from these registries.
pnpm store add now prepares the store for offline installs from package tarballs downloaded some other way. After pnpm store add ./tarballs/*.tgz, pnpm install --offline --frozen-lockfile installs each registry package whose lockfile entry pins one of those tarballs #2978.
Custom pnpmfile fetchers can use fetchers.gitHostedTarball, fetchers.git, and fetchers.binary pnpm/tasks#191.
Running node or pnpm install in a project that pins a Node.js version pnpm has not downloaded yet no longer hangs when a globalPnpmfile is configured #17530.
pnpm install with enableGlobalVirtualStore no longer fails on Windows for a dependency from a named registry, such as gh: or npmjs: #17665.
Concurrent installs that share a global virtual store no longer fail with ERR_PNPM_CMD_SHIM_SYMLINK_BIN when they link the same executable at the same time #17587.
pnpm install and pnpm ci now succeed when dependency skills are approved but no agent skill directory exists. The skills stay unlinked until a directory exists #17574.
Commands run from a workspace package now use the same default store as the workspace root. Before, pnpm add in a package could fail with ERR_PNPM_UNEXPECTED_STORE when the workspace root was its own mount point and the home store was on another volume, as in a sandbox or a container.
A workspace installed with the old behavior may need one pnpm install --force from the workspace root.
pnpm deploy now keeps a symlink in the project whose target is missing from the source, such as a link into a node_modules directory that was removed after the build. Deploy used to drop such a link silently #17571.
pnpm install now links the runtime that an earlier pnpm install --no-runtime skipped, and pnpm install --no-runtime removes a runtime that an earlier install linked #17542.
With enableGlobalVirtualStore, pnpm install again runs a dependency's build scripts in a project whose global virtual store slot another project already built, unless the side-effects cache has build output to restore for it. A build that writes only outside its own package, such as a git hook installer, now takes effect in every project #17526.
Commands of a package whose bin paths contain excess parent directory segments, such as ../dist/cli.js, are no longer missing. Such paths now resolve inside the package #17586.
Generated POSIX shell shims now quote their paths, so shell special characters in a path stay literal.
Packages from the default registry keep plain lockfile keys, even when a prefix such as npmjs points at the registry set as registry. A dependency written with such a prefix shares the plain entry of the same package. The next install rewrites keys that earlier versions qualified this way #17575.
pnpm install --frozen-lockfile, pnpm approve-builds, and pnpm rebuild now accept a lockfile that resolves a * dependency to a prerelease latest version. pnpm wrote such a lockfile and then reported it as outdated #17594.
pnpm install --frozen-lockfile now accepts a lockfile written with excludeLinksFromLockfile and linkWorkspacePackages on, when a project depends on a workspace package through a catalog: entry. It used to fail with ERR_PNPM_OUTDATED_LOCKFILE.
pnpm install --frozen-lockfile no longer rejects a freshly generated lockfile when addMissingPeerTypes is enabled and an injected workspace package has peer dependencies #17668.
Relative local paths in root overrides now resolve from the workspace root when each project has its own lockfile #17691.
Installing a local directory dependency no longer fails when another project's install is writing a lockfile in that directory.
Relative local paths in root catalogs now resolve for dependencies and peers #17690.
pnpm install now resolves auto-installed relative workspace: and file: peers from the directory of the package that declares them #17676, #17689.
pnpm dedupe --check leaves pnpm-lock.yaml untouched while it looks for deduplication changes. If configDependencies changed since the last install, the check keeps the lockfile they sync, as pnpm install does #17628.
pnpm dedupe --check no longer fails when the only difference is the integrity of a locked version that the registry now reports with a stronger algorithm, such as a sha512 integrity replacing the sha1 shasum it reported when the lockfile was written #17692.
Peer deduplication no longer gives a project different copies of a dependency across direct and transitive paths when an optional peer has no provider #17666.
Dependencies no longer bind to another project's peer variant when the provider has nested peers, including providers that finish resolving later #17593.
Re-resolving a lockfile no longer preserves optional peer bindings from other projects when no provider is in scope #17592.
pnpm peers check warns when a required peer is resolved without a provider declared by the project or its dependency ancestors, with autoInstallPeers: false and dedupePeerDependents: true. These warnings do not change the command's exit code or cause strictPeerDependencies failures.
pnpm install, and pnpm run and pnpm exec with verifyDepsBeforeRun, no longer read the package.json of workspace projects whose files did not change since the last install. This also holds with a pnpmfile, configDependencies, or sharedWorkspaceLockfile: false. In an up-to-date workspace with sharedWorkspaceLockfile: false, pnpm install no longer runs the install of each project pnpm/tasks#256.
A recursive pnpm run or pnpm exec with verifyDepsBeforeRun set no longer reads every package.json in the workspace once per project when sharedWorkspaceLockfile is false. In a 300-project workspace, pnpm -r exec true went from 490 ms to 42 ms pnpm/tasks#256.
pnpm install makes fewer stat calls when it hardlinks files from the store, as few as 12.7.0 made #17543.
Picking versions from registry metadata uses less temporary memory.
With verifyDepsBeforeRun, pnpm run and pnpm exec now report dependencies as out of date after a dependency is added to the package.json of a local directory dependency, such as "lib": "file:../lib". Before, the command ran without the new dependency installed.
verifyDepsBeforeRun no longer reports a file: directory dependency as out of date after an edit to package.json that leaves its dependencies unchanged #17697.
verifyDepsBeforeRun no longer reports dependencies as out of sync when only the version field of a single-project repository changed #17560. The same holds for a workspace project that no dependency can resolve to. A script run after such a change no longer starts an install first.
A repeat pnpm install now rewrites the bin shims after extendNodePath changes. Before, it reported "Already up to date" and the shims kept the NODE_PATH of the previous setting.
pnpm add <pkg> without a version now saves the range that the other workspace projects declare for the package, or the one a matching override sets. A catalog: reference still comes first, and the tag setting is used only when none of these exists pnpm/tasks#191.
pnpm update with only negated selectors, such as pnpm update '!foo', now leaves the dependencies listed in update.ignoreDeps unchanged. Negated crate: and pypi: selectors, such as !crate:sha2, now exclude that dependency and update the rest pnpm/tasks#243.
pnpm update --latest keeps three kinds of Cargo dependencies where they are, unless the crate is named on the command line. Before, it moved each one to the newest release and left a workspace that did not build.
tower-0-4 = { package = "tower", version = "0.4" }, stays within its requirement if the workspace also declares the crate under its own name.[patch.crates-io] keeps its version, with a warning.pnpm update crate:foo@1, moves it back.Other new major versions are still selected and may need code changes.
pnpm update now keeps a Cargo dependency at its current version, with a warning, if the new version lacks a feature the workspace enables on it. If the crate is named on the command line, as in pnpm update --latest crate:sha2, the update fails with an error that names the missing features.
pnpm update now keeps the operator of every existing Cargo requirement, so ~1.0.0 is updated to ~1.1.0, and an exact = requirement stays exact unless the selector gives a range, such as crate:foo@^2. The savePrefix and saveExact settings apply only to new Cargo dependencies. Saved Cargo requirements omit build metadata.
pnpm update now updates a Cargo dependency whose inline table spans several lines, such as one with a multi-line features array. It failed with "its Cargo.toml dependency declaration is not a string or single-line inline table".
pnpm update no longer applies the savePrefix and saveExact settings to Python requirements. A savePrefix such as ^ made pnpm update fail in a project with Python dependencies.
pnpm update now keeps the precision of a ~= requirement, so ~=1.0 is updated to ~=1.5 and still allows any 1.x release. With --latest, a ==1.* requirement is updated to ==2.*.
pnpm store prune now keeps packages linked from a configured modules directory pnpm/tasks#230.
pnpm store prune now removes aliases of pruned packages.
pnpm store status no longer reports untouched packages as modified when the global virtual store is enabled. If the installed global-store layout cannot be verified, the command reports ERR_PNPM_STORE_STATUS_UNVERIFIABLE and asks for a reinstall #17631.
pnpm store add now fails with ERR_PNPM_FROZEN_STORE_WRITE when frozenStore is enabled. It used to write package files into the read-only store without recording them, so no install could use them.
pnpm cat-index <name>@<version> no longer shows the index of a package whose name differs only in letter case.
pnpm link now fails without changing package.json or pnpm-workspace.yaml when the linked package's name is not a valid npm package name. It used to write that name to both files, which made every later install fail #17475.
pnpm link <dir> now resolves a relative <dir> against the current directory. In a directory without a package.json, such as a workspace's packages folder, pnpm link . used to link the nearest project above it into itself #17475.
A Node.js version range such as >=26.13, for example in devEngines.runtime, now resolves to the newest stable release that satisfies it. pnpm picks a prerelease only when no stable release matches #17516.
Switching to the pnpm version a project pins no longer writes a temporary _tmp_* file into the project directory, which file watchers reported on every command #17681.
pnpm now reads the linkWorkspacePackages, injectWorkspacePackages, extendNodePath, frozenStore, and optimisticRepeatInstall settings from PNPM_CONFIG_* environment variables, such as PNPM_CONFIG_LINK_WORKSPACE_PACKAGES=true. --config.extend-node-path now applies too.
Recursive scripts run with --sequential or --workspace-concurrency=1 print GitHub Actions log groups again #17629.
When pnpm docs cannot open a browser, the URL it prints no longer includes the query string or the fragment.
pnpm 12.17.0 adds pnpm peers check --global , dependency-group selectors and wildcards in overrides , and runtime, package manager, Cargo, and Python
pnpm 12.17.0 adds pnpm peers check --global, dependency-group selectors and wildcards in overrides, and runtime, package manager, Cargo, and Python updates in pnpm outdated and pnpm update. It also fixes files that other users could not read in Docker images, and repeat installs that missed changes to local dependencies.
pnpm peers check now accepts --global (-g) to check globally installed packages. After a global install or update, the peer dependency warning now suggests pnpm peers check -g #17504.
pnpm outdated and pnpm update now inspect and update package manager and runtime versions in devEngines.packageManager, packageManager, devEngines.runtime, engines.runtime, and runtime: dependencies. With cargo.enabled or python.enabled, pnpm outdated and pnpm update also inspect and update Cargo dependencies in Cargo.toml and Cargo.lock and Python dependencies in pyproject.toml and pylock.toml.
overrides selectors now support :prod, :optional, and :peer pseudo-selectors that target a single dependency group. They also support * wildcard patterns on parent and target package names. An override with a non-range value, such as npm: or file:, no longer adds a peer dependency to dependencies. Removing an optional dependency with "-" now also removes the duplicate entry from dependencies #5391.
Files that pnpm creates in a project now get the permissions the umask gives any new file, such as 0644. Before, several of them were readable only by the user who ran pnpm, which broke Docker images that run as a different user #17435.
The fix applies to:
node_modules/.pnpm-workspace-state-v1.json. A different user running pnpm run reinstalled the dependencies because it could not read this file.pnpm-workspace.yamlpnpm deploypnpm patch-commitpnpm dedupe --checkWhen pnpm edits an existing file, the file keeps its permissions.
pnpm install no longer writes broken dependency links when the project's node_modules is a symlink to another directory, such as another project's node_modules. The install reported success, but the links it wrote did not resolve #17448.
Commands installed with pnpm add --global now find the dependencies that pnpm hoists for their package. A package that loads a dependency it does not declare, such as a native addon's platform-specific package, failed with "Cannot find module". Reinstall such a package with pnpm add --global to update its existing command #17503.
When pnpm switches to the version a project pins, it now installs that version's native binary for the current host, even if the project's supportedArchitectures excludes the host. Before, pnpm could not use the pinned version and kept running the installed one. pnpm also repairs a pinned version that an earlier install left without the host's binary.
With the global virtual store, a change to a dependency of one package in a dependency cycle now gives every package in that cycle a new directory. Before, the other packages kept their directories and still linked the old copy of the changed package, so the project could load two copies of it #17466.
Packages in a dependency cycle, and packages that depend on one, move to new global virtual store directories once after this update. Those that run a build miss the side-effects cache once.
With nodeLinker: hoisted, when two workspace projects need the same package version and it cannot be hoisted to the root, each project now keeps the copy installed in its own node_modules. Build scripts run in each of these copies. Before, the second project's copy was replaced with a symlink to the first project's, so every repeat install imported it again #17498.
The Node.js latest selector now chooses the newest stable release #17490.
Hardlinking from the store now stats each store file once per install. Since pnpm 12.8.0, a store file was stat'ed again for every package that links it. On an offline install of a large workspace, that added up to 15% system CPU #17500.
pnpm install --frozen-lockfile no longer reports an outdated lockfile right after the install that wrote it. This happened when a pnpmfile readPackage hook or packageExtensions changed the dependencies or peer dependencies of a local directory dependency outside the workspace projects. It affected a file: dependency, an injected workspace:../dir dependency outside the workspace patterns, and an injected workspace package left out by --filter #17447 #17473.
A repeat pnpm install now takes the fast path when ignoredOptionalDependencies removes an optional dependency of a file: directory dependency. It used to resolve again on every run.
pnpm install now resolves again after an edit to an injected workspace:../dir dependency outside the workspace patterns under a shared lockfile. It used to keep the lockfile unchanged. The next pnpm install --frozen-lockfile then failed #17476.
pnpm install now resolves a local directory again after its package.json changes when an override or a package extension adds it to the dependencies of a registry package. pnpm install --frozen-lockfile fails on a lockfile that still records the old dependencies of such a directory #17486.
With injectWorkspacePackages and per-project lockfiles, pnpm install now updates a project's lockfile when a local tarball that an injected workspace project depends on is replaced. The project's lockfile kept the old version and integrity before.
pnpm install now detects a change to a local tarball or directory that only a pnpmfile readPackage hook depends on. A repeat install reported "Already up to date" and kept the old contents before pnpm/tasks#227.
pnpm install now relinks a workspace: or link: dependency whose link was deleted from node_modules. It used to report "Already up to date" and leave the link missing #17485.
A repeat pnpm install reports "Already up to date" again when a pnpmfile readPackage hook changes the dependencies of a workspace project. Since 12.15.0, every such install ran in full #17468.
After an edit to a project's package.json, pnpm install and verifyDepsBeforeRun now run the pnpmfile's readPackage hook on the edited manifest before comparing it with the lockfile. They could report the project up to date when the hook rewrote the edited dependency to a specifier the lockfile did not record.
pnpm update --latest with package selectors now updates the dependencies of the selected packages within their declared ranges. Excluded packages and their dependencies keep their locked versions #17444.
pnpm add <pkg>@<tag> now uses a catalog entry set to that same dist-tag. The dependency is saved as catalog: and the entry stays as written pnpm/tasks#225.
When pnpm add adds a new dist-tag such as vue@legacy to a catalog, the catalog entry records the exact version the tag points to. The same applies to a dependency added without a version when the tag setting names a dist-tag other than latest.
pnpm add now saves the resolved version range of an npm alias. For example, pnpm add v2@npm:vue and pnpm add v2@npm:vue@^3.0.0 both save npm:vue@^3.5.13.
Programs that a script or pnpm exec command leaves running, such as a browser opened by the open package, now outlive pnpm exactly when they would outlive the command run without pnpm. Before, on Windows, a failed command, Ctrl+C, or a closed terminal ended all of them. pnpm still ends them when it is killed or crashes.
When a recursive or parallel run bails, the scripts still running now receive SIGTERM on Unix and are killed only if they are still running two seconds later. On Windows, everything those scripts started is ended, including detached processes whose parent has already exited. Before, a bail killed them at once #17465.
On Windows, the shell shim of a .cmd or .bat bin now runs it under Git Bash when MSYS argument conversion is off, such as with MSYS_NO_PATHCONV=1 or MSYS2_ARG_CONV_EXCL='*'. The shim used to start an interactive cmd.exe prompt #17480.
pnx and pnpm create now run the command in the directory selected by --dir or --workspace-root. Without either flag, the command still runs in the directory pnpm was started in.
pnpm --env-file now reads files the way node --env-file does. Values are taken as written, so $VAR is no longer expanded and Windows paths such as C:\Users\me load unchanged. A file is no longer rejected for its contents.
pnpm version no longer creates a git commit and tag when gitTagVersion is set to false #17460.
pnpm publish now reads the publishBranch setting from pnpm-workspace.yaml and from PNPM_CONFIG_PUBLISH_BRANCH. The --publish-branch flag overrides it.
pnpm now accepts --strict-ssl and --local-address <ip> on the command line.
pnpm doctor uses a 15-second timeout when checking registry connectivity.
pnpm-workspace.yaml parse errors now report ERR_PNPM_INVALID_SETTING.
The error for a dependency with an invalid name in a project's manifest now names the project's directory. It used to say only "The current package", which did not tell which workspace project to fix #17475.
This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by
This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.
pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.
pnpm pack and pnpm publish now apply a files entry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as !dist/index.js, stays out even when a later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.
pnpm install no longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.
pnpm install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is false pnpm/tasks#224.
pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #17402.
pnpm install now reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.
Commands, pnpm --version, pnpm self-update, and invocations with unknown flags now apply the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.
pnpm now accepts the --cache-dir <dir> flag, as in pnpm install --cache-dir /tmp/pnpm-cache #17422.
When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. Before, the error suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.
Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #17388.
This release adds a global --env-file flag, updates to a symlinked pnpm-lock.yaml, and pnpm setup --no-modify-path. It also fixes two security issues, in zstd decompression and in signing.
Added a repeatable global --env-file <path> flag to load environment variables from dotenv-style files before running a command. Later files override earlier files, variables already in the environment are preserved, and loaded variables are visible to user-level .npmrc interpolation and lifecycle scripts #7111.
pnpm can now update a pnpm-lock.yaml that is a symlink. List the directories the lockfile may link into in the symlinkedLockfileTargetDirs setting, in the global config or with PNPM_CONFIG_SYMLINKED_LOCKFILE_TARGET_DIRS. pnpm writes the update to the file the symlink points to if that file is inside one of these directories. The symlink stays in place. pnpm ignores this setting in pnpm-workspace.yaml #17222.
Added a --no-modify-path option to pnpm setup. It installs pnpm without adding it to PATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged. pnpm setup then prints the lines to add yourself get.pnpm.io#37.
Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #17388.
Signing in pnpm and pnpr no longer uses arithmetic that may leak the private key through timing. This covers shared artifacts, OCI registry tokens, and OIDC login state advisory.
A dependency symlink that pnpm cannot point at the wanted target now fails the install with an error that names the link. This happens when the filesystem still serves the old link after pnpm removed it, as a node_modules served by a virtual filesystem does. pnpm used to remove the link again without end and crashed with a segmentation fault once the thread ran out of stack.
Concurrent workspace installs no longer lose store-index rows when initializing the shared SQLite index #17388.
Agent skill links now keep the same target across installs when a package version is installed with several sets of peer dependencies. An install no longer fails with ERR_PNPM_AGENT_SKILL_PATH_OCCUPIED on a skill link that pnpm created for another of those copies #17319.
pnpm now fails at once, without retrying, when a downloaded package archive contains a rejected entry path #17205.
pnpm now builds a git-hosted dependency in every new location it links the dependency into, such as a new global virtual store slot or a fresh node_modules. When the side-effects cache holds the build output, pnpm restores it from there. Before, only the install that fetched the dependency built it. This also fixes dependencies that are already in the store #17224.
Changes a preResolution hook makes to the lockfiles now take effect. The hook now also runs when pnpm installs from an up-to-date lockfile. An error thrown by the hook now fails the install.
A custom fetcher in the pnpmfile can now call fetchers.directory to fetch a package from a local directory. The call rejects with ERR_PNPM_TARBALL_INTEGRITY if the lockfile pins an archive integrity for the package. Previously, calling fetchers.directory failed with a TypeError.
packageImportMethod: copy now also applies to packages that have lifecycle scripts or patches. On a filesystem that supports block cloning, such as ReFS or a Dev Drive on Windows, these packages were cloned #17195.
With nodeLinker: hoisted and autoInstallPeers: false, a package that workspace projects use with different peer versions is now installed once per peer variant, so each project's copy resolves that project's peer #17395.
Under nodeLinker: hoisted, pnpm install now leaves a patched package that is already in place alone. The same holds for a package whose peers include a patched package, such as every package peering on a patched react-native #17188.
With nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package in node_modules.
A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".
storeDir or virtualStoreDir: it recreates node_modules.globalVirtualStoreDir: it links the packages from the new directory.virtualStoreDirMaxLength: it renames the virtual store directories.dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.trustLockfile turned off: it verifies the lockfile.pnpm add, pnpm remove, and pnpm update now fail if node_modules does not match the current settings. Run pnpm install to recreate it. Previously, these commands removed and reinstalled node_modules without asking. They report:
ERR_PNPM_UNEXPECTED_STORE if node_modules was linked from a different store.ERR_PNPM_UNEXPECTED_VIRTUAL_STORE if it was linked from a different virtual store directory.ERR_PNPM_MODULES_BREAKING_CHANGE if it was installed by an incompatible pnpm version, or if node_modules/.modules.yaml cannot be read.ERR_PNPM_NODE_LINKER_DIFF if it was installed with a different nodeLinker.pnpm update now also fails with ERR_PNPM_HOIST_PATTERN_DIFF and the other errors pnpm add reports for a changed hoist pattern or virtualStoreDirMaxLength.
An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modules pnpm/tasks#217.
pnpm install and the verifyDepsBeforeRun check now notice an edited patch file when sharedWorkspaceLockfile is false.
pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.
pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #17324.
pnpm install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field pnpm/tasks#211.
A package that a plain range and a <prefix>: specifier both resolve from one registry is now recorded once in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in registries or through namedRegistries, the package is keyed <name>@<prefix>:<version> however its dependency was written: with the prefix, as a plain range its scope routes to that registry, or through the default registry. Before, the plain range was keyed <name>@<version>, so one tarball was installed twice and instanceof checks and module singletons broke between the two copies. The same name and version served by two registries still get separate entries. When several prefixes declare one registry, its packages are keyed by the lexicographically smallest prefix.
If a scope you route reaches a registry that also declares a prefix, your next pnpm install re-keys those entries, which shows up as a lockfile diff. Commit it. pnpm install --frozen-lockfile installs the lockfile as recorded.
pnpm install now resolves a scope's packages again when the scope is routed to another registry in registries. Before, the lockfile kept the versions and integrity resolved from the old registry, so the install failed when the new registry did not serve a locked version or served different content. pnpm records in the workspace state which registry each scope routed to, so a fresh clone without that record installs the lockfile as recorded. Changing the default registry resolves nothing again, and pnpm install --frozen-lockfile is unchanged.
When autoDedupe is off, a workspace project's dependencies now resolve from its own ranges, like they do with sharedWorkspaceLockfile: false. Previously, another project's narrower range could hold them back. For example, ajv: "*" now resolves to the latest Ajv even if another project depends on ajv@^6. Packages that a project lists in peerDependencies still follow the versions other projects use. pnpm dedupe and installs with autoDedupe: true still pick one version that satisfies every range. Set autoDedupe: true if CI runs pnpm dedupe --check #17235.
An optional dependency written with a named-registry prefix, such as work:^1.0.0, now fails the install when it cannot be resolved but the lockfile already has a matching entry from that registry. Such a dependency was skipped, which removed its entries from the lockfile.
With injectWorkspacePackages: true, a workspace: dependency written as a relative path, such as workspace:../lib-a, in a workspace package now resolves from that package's directory #17284.
Fixed pnpm install failing with ERR_PNPM_UNSUPPORTED_PROTOCOL when a workspace package injected through a relative path, such as workspace:../lib, has catalog: dependencies. Their catalog entries now resolve the way they do for a package injected by name #17280.
pnpm dedupe now refreshes cached registry metadata while re-resolving locked versions #17208.
pnpm dedupe --check no longer fails when the only difference is a deprecated notice that the registry added or removed after the lockfile was written #17198.
Installs delegated to a pnpr server now resolve every prefix declared for a registry URL. A dependency or lockfile entry that used the second of two prefixes for the same registry, such as zeta: next to work: in namedRegistries, failed on the server pnpm/tasks#204.
Registry revisions are now addressed at <registry>/<name>@<version>+r<revision> pnpm/tasks#208.
pnpm add <pkg>@<tag> and pnpm add <pkg>@<range> now install the version the tag or range resolves to, even when the saved range allows a newer one #17234.
pnpm add <pkg> without a version now installs the version under the dist-tag set by the tag setting. An npm: alias or a jsr: dependency without a version resolves that tag too. The setting is read from pnpm-workspace.yaml, the global config, PNPM_CONFIG_TAG, and --config.tag, and defaults to latest.
pnpm add now accepts the lowercase short options -p, -d, -o, and -e as aliases of --save-prod, --save-dev, --save-optional, and --save-exact.
pnpm -D install <pkg> now saves the package to devDependencies. An add option such as -D or -E written before install <pkg> was rejected as an unexpected argument.
pnpm add -T now reports that the short option is ambiguous and points to --save-types and --tilde.
Global packages installed with pnpm add -g are now linked from the global virtual store, so global packages that share dependencies share one copy. Set virtualStoreType: project to give each global install its own virtual store.
pnpm add -g and the other --global commands now fail with ERR_PNPM_CONFIG_CONFLICT_VIRTUAL_STORE_DIR_WITH_GLOBAL when --virtual-store-dir is passed. A custom --hoist-pattern fails with ERR_PNPM_CONFIG_CONFLICT_HOIST_PATTERN_WITH_GLOBAL. Passing --link-workspace-packages, --shared-workspace-lockfile, or --config.lockfile-dir with --global also fails, with the matching ERR_PNPM_CONFIG_CONFLICT_*_WITH_GLOBAL code.
pnpm now reads the strictSsl and localAddress settings from pnpm-workspace.yaml, the global config.yaml, PNPM_CONFIG_* environment variables, and --config.* options. This includes pnpm self-update and the download of the pnpm version pinned in packageManager. Before, pnpm read them only from .npmrc as strict-ssl and local-address and ignored the other sources pnpm/tasks#201.
When Corepack runs pnpm and the native binary has to be downloaded, the download now uses the proxy from pnpm's config. That proxy comes from PNPM_CONFIG_HTTPS_PROXY and the matching variables, the global config.yaml, and the user .npmrc. Previously, the download read the proxy only from HTTPS_PROXY, HTTP_PROXY, and NO_PROXY pnpm/tasks#215.
When the pnpm package downloads its native binary on first run, as it does under Corepack, it now trusts the CA certificates from the ca, ca[], and cafile settings of .npmrc, including the ones scoped to the registry. A registry behind a private CA failed with fetch failed before, unless NODE_EXTRA_CA_CERTS named the CA. A project .npmrc is used only while the download is checked against npm's signature. Node.js versions that cannot add CA certificates after startup still need NODE_EXTRA_CA_CERTS.
pnpm login saves the token in <pnpm config>/auth.ini again. Since v12.1.0, an unscoped login had made its registry the default for every project that did not name a registry. A login now also removes the token an earlier login saved for that registry or scope under _auth in the global config.yaml. pnpm login --scope still routes the scope through the global registries setting.
pnpm no longer warns that a registries entry routed through the @ scope matches no configured registry. pnpm applied such an entry and its options such as serverType while reporting it as ignored pnpm/tasks#184.
pnpm ci --lockfile and pnpm ci --config.lockfile=true no longer delete pnpm-lock.yaml. pnpm ci now always keeps the lockfile and runs a frozen install from it.
pnpm deploy --legacy now checks the workspace lockfile against minimumReleaseAge and the other resolution policies, as pnpm install does, and fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION when a locked version is too new. It used to deploy an older version that is not in the lockfile without a warning #17209.
pnpm deploy now keeps a deployed symlink to a directory inside the project even if the directory is not among the deployed files, such as a link into node_modules #17288.
pnpm pack and pnpm publish now keep pnpm.config in the published package.json. They also always include the file pnpm.config points to in the tarball #17210.
pnpm -r publish --batch now sends PUT /-/pnpr/v0/publish, the batch publish endpoint that pnpr serves.
pnpm audit --ignore and pnpm audit --ignore-unfixable now exit with a non-zero code when vulnerabilities at or above the audit level remain after ignoring. Before, these commands always exited with code 0.
pnpm audit --fix and pnpm audit --interactive now fail with ERR_PNPM_AUDIT_FIX_WITH_IGNORE when combined with --ignore or --ignore-unfixable. Before, the fix ran and the ignore flags had no effect.
pnpm -r run <script> now honors the requiredScripts setting from pnpm-workspace.yaml. If the script is listed there and a selected project does not define it, the run fails with ERR_PNPM_RECURSIVE_RUN_NO_SCRIPT and names the projects that lack it.
pnpm run and pnpm exec no longer report the dependencies as out of date after a lockfile change when dedupePeers is true #17322.
On macOS, killing pnpm while it runs scripts in several projects at once now ends every one of those scripts. Before, a script could keep running after pnpm died.
pnpm run, pnpm exec, and pnpm dlx no longer dump a core file for pnpm itself when a command they started dies from a signal #17204.
The runtime setting is now read. Setting runtime: false in pnpm-workspace.yaml, pnpm_config_runtime=false, or --config.runtime=false stops pnpm install, pnpm add, pnpm dedupe, and the other installing commands from installing the runtimes in devEngines.runtime and engines.runtime. pnpm dedupe now also accepts --no-runtime.
Directory selectors with legacyDirFiltering: true now include the project in the named directory along with its descendants. Excluding a directory also excludes that project pnpm/tasks#196.
pnpm help --all and pnpm help -a now print the full list of commands. They used to fail with an "unrecognized subcommand" error.
Reading the file-creation mask on Linux no longer sets it. pnpm had to replace the mask to learn what it was, and a file another thread created in the window between the two calls was created unmasked.
pnpm now passes an interrupt on to the handler it replaced, with the arguments that handler expects. A handler that asked for the signal's details was called without them. Only a program that embeds pnpm and installs its own SIGINT, SIGTERM or SIGHUP handler was affected.
pnpm store prune now keeps the packages that a project still uses when pnpm copied or cloned them into node_modules. These include patched packages, built packages, and every package installed with packageImportMethod: copy. Before, the prune removed them, and the next install downloaded them again #7192.
pnpm store prune now keeps the packages of a project when the store path reaches its directory through a symlink. Previously, prune dropped such a project from its list and removed the packages only that project used from the global virtual store.
pnpm store prune now removes the package metadata cache, the metadata* directories in the cache directory. This clears the outdated integrity checksums that cause ERR_PNPM_TARBALL_INTEGRITY when a registry republishes a version.
pnpm install resolves dependencies faster in large workspaces on Linux, macOS, and Windows on x64 and arm64.
Sped up cold installs and pnpm fetch on macOS. pnpm now links downloaded packages into the virtual store on a separate thread, so a slow link pass no longer pauses the downloads that are still in flight #17271.
Sped up installs that add new projects to a workspace with a peer-heavy lockfile. pnpm now reads the lockfile's locked peer versions once for all new projects #17311.
Warm installs no longer read the package.json of every git-hosted dependency. pnpm now stores the manifest of a git-hosted package in the store index when it fetches the package.
pnpm update --depth <n> with a large n, such as the --depth=9999 that update-browserslist-db runs, now finishes as fast as --depth Infinity. It used memory and stack in proportion to n on lockfiles with dependency cycles, and could run out of memory or crash #17329.
Output that fills the terminal, such as pnpm run --stream script output, is now written once. Before, every new line also rewrote all the lines already on screen #17387.
pnpm now warns when a pnpmfile defines the importPackage hook. pnpm does not run this hook. Use the packageImportMethod setting to choose how packages are written to node_modules.
pnpm now warns when a project's pnpm-workspace.yaml sets ci, globalShims, or tools, and names where to set them instead. These settings were already ignored there without a warning. pnpm config set also refuses to write them to a project's pnpm-workspace.yaml.
pnpm no longer documents the scriptsPrependNodePath setting, which has no effect. A pnpm-workspace.yaml that sets it still loads.
pnpm deprecate and pnpm unpublish now work for packages whose registry metadata is larger than 10 MiB, such as typescript. They accept up to 50 MiB, t…
This release lets pnpm-workspace.yaml delegate settings to other files and config dependencies with include, adds lockfile.integrityTarget: tar and tar-registry support, accepts zstd-compressed registry responses, and honors SOURCE_DATE_EPOCH in pnpm deploy and pnpm install. It also rejects registry metadata that names a different package than the one requested and speeds up workspace installs and macOS file linking.
pnpm-workspace.yaml can now delegate settings to other YAML files and to config dependencies through a new include field. Each source may define only the settings the root manifest delegates to it. Every setting has one owner. Commands that change settings write each one to the file that owns it. A relative path in an included file is relative to that file. See Splitting Settings Across Files.
A config dependency supplies its settings through the YAML file named in the pnpm.config field of its package.json. The new bootConfig setting sets the release-age and trust policy pnpm uses to install config dependencies and the pnpm version from packageManager.
Added the lockfile.integrityTarget setting. With integrityTarget: tar, pnpm-lock.yaml pins the hash of every package's uncompressed tar, so the lockfile no longer changes when a registry recompresses its tarballs or serves them as tars. pnpm learns a version's tar hash from the store or by downloading it once. pnpm audit signatures ties the tar hash to the signed .tgz integrity.
lockfile:
integrityTarget: tar
pnpm can now install from a registry that serves uncompressed tars with zstd or gzip content coding. pnpm-lock.yaml records the hash of each tar. Declare such a registry with serverType: pnpr in registries to keep tarball URLs out of the lockfile. See Tar registries.
pnpm now decodes the content coding of tarball downloads itself. It rejects a zstd response whose window is larger than 8 MiB.
Added the maxTarballUnpackedSize setting. It caps the bytes the files of one package may unpack to, 4 GiB by default.
Registry revisions now always pin the hash of the uncompressed tar, the original included. pnpm records an original selected through the revision protocol, for example with a +r0 specifier, as revision: 0 in the lockfile and fetches it from the registry's digest route. pnpm checks a revision's tar whether the registry sends it as a tar, gzip, or zstd. Revision metadata must list revision 0 and mark the selected revision. pnpm rejects incomplete revision metadata with ERR_PNPM_MALFORMED_METADATA.
pnpm now accepts zstd-compressed responses. Registries that serve zstd send package metadata in fewer bytes than with gzip, most of all the full metadata that settings such as minimumReleaseAge and trustPolicy read.
pnpm deploy and pnpm install now use the SOURCE_DATE_EPOCH environment variable as an upper bound for timestamps in node_modules/.modules.yaml and node_modules/.pnpm-workspace-state-v1.json. With an equivalently prepared deploy target and an epoch no later than the timestamps that would otherwise be recorded, deploying the same project twice produces identical files #17171.
pnpm update --interactive now highlights the row under the cursor in cyan while keeping the colors of its version changes.
pnpm now fails with ERR_PNPM_REGISTRY_NAME_MISMATCH if a registry returns metadata for a package other than the one requested. Before, pnpm installed the package under the name in the metadata, so allowBuilds rules for the requested package did not apply to it.
minimumReleaseAgeExcludePrune and trustPolicyExcludePrune now keep exclusions for resolved configuration dependencies and their transitive dependencies #17142.
When pnpm install resolves a dependency again, it now reuses a version that the install already resolved for the same package, as a fresh install does. Before, it kept the version the lockfile pinned and added a second copy of the package. A locked version still stays when nothing else in the install prefers another version. To pin a transitive dependency on purpose, use overrides #17084.
When another workspace project adds a different version of a package, a project's auto-installed peer on that package now moves to the version a fresh install picks. It used to stay on its locked version while any other project still accepted that version #17058.
A package that lists the same dependency in dependencies and as an optional peer now gets the peer bound when a project adds a provider for it later. The lockfile now records every peer a package declares, including one its own dependency supplies #17056.
pnpm install --prod and pnpm deploy --prod no longer drop a dependency that a package declares both as an optional peer and as its own dependency, when the package resolved it as its own dependency and a dev dependency provides the same package under another alias.
pnpm install with an existing lockfile and a second pnpm dedupe now keep optional peer bindings that point into a dependency cycle or back into the dependent package. Before, the second run dropped the optional peer binding from the lockfile snapshot key.
pnpm install and pnpm dedupe now preserve own-dependency and peer-dependency bindings when reusing a lockfile whose peer suffixes were hashed by peersSuffixMaxLength.
Upgrading a direct dependency in one workspace project now refreshes matching transitive pins in sibling projects during the same pnpm install pass.
With resolvePeersFromWorkspaceRoot: false, a workspace project no longer binds a peer to a version that only another project's dependencies provide. pnpm now auto-installs a version that satisfies the peer range for that project. Before, the project got a version outside the range, with no peer warning.
pnpm install, pnpm add, and pnpm update now reuse the lockfile's resolution for dependencies that take part in a dependency cycle, such as mlly and pkg-types. They re-resolved those packages and everything that depends on them from the registry before pnpm/tasks#130.
pnpm now measures a pnpm.overrides entry written as a workspace: path, such as workspace:./packages/foo, from the directory holding pnpm-workspace.yaml. It used to be measured from each package the override rewrote. The install then linked a directory that does not exist, or failed if workspace packages were injected #17010.
pnpm install now removes config dependencies that are no longer declared, including when the entire configDependencies setting is removed. Frozen installs reject a lockfile that still records removed config dependencies.
pnpm install --update-checksums now re-resolves every locked package and records the integrity the registry reports now.
pnpm add and pnpm install now accept gist:<id> dependencies and GitHub Gist URLs, and install them from the gist's archive. pnpm pkg fix normalizes a gist: repository the way npm pkg fix does, pnpm licenses links a gist package to its gist page, and pnpm sbom reports the repository of a package whose repository field is a gist: shorthand.
pnpm add now reads the package name correctly from a tarball URL under a registry URL that has a path, such as https://example.com/npm/, and installs a registry tarball URL with a malformed percent escape as a plain tarball URL. Before, the registry path became part of the name, so a scoped package failed with ERR_PNPM_INVALID_PACKAGE_NAME.
With minimumReleaseAge set, pnpm now revalidates a package's cached full metadata with a single ETag request so an unchanged registry answers with 304, even when the registry does not list a publish time for every version. Previously, pnpm downloaded that metadata again whenever the cached copy was older than minimumReleaseAge. With resolutionMode set to lowest-direct or time-based, pnpm also reuses that metadata across every workspace project that depends on the package.
When pnpm revalidates cached registry metadata, it now sends If-Modified-Since when the registry's modification time is a date without a time, and no longer crashes when the modification time is before 1970.
Added protocol versioning between the pnpm client and pnpr server, verified applied resolution policies in resolution responses, and preserved structured error codes across the wire.
Sped up pnpm install on macOS. On a 12-core Mac, installing 1352 packages from a warm store took 1.3 seconds, down from 2.2. pnpm now writes package files into node_modules with 4 threads on macOS, whatever the number of CPU cores. Set the PNPM_MACOS_LINK_THREADS environment variable to use a different number of threads, or to 0 to write files with the threads pnpm uses for the rest of the install.
pnpm install is faster and uses less memory in large workspaces with sharedWorkspaceLockfile: false. Each project's install no longer reads the manifests of every other workspace project again. Installs that wait for their workspace dependencies now count toward workspaceConcurrency #16966.
Sped up workspace project discovery, dependency resolution, lockfile up-to-date checks, and peer dependency checks in large workspaces #16839 pnpm/tasks#9. On a workspace with 6,833 projects, the lockfile up-to-date check uses about 1 second less CPU time. The peer dependency check at the end of an install now checks linked workspace projects against the manifests already in memory, without reading each package.json again.
Sped up bin linking and build planning during pnpm install. Package binary targets and shebang runtimes are now precalculated during tarball extraction and served in pnpr registry metadata alongside verified requiresBuild, tarball size, and file-count metadata.
Lowered peak memory when pnpm downloads many packuments, such as during lockfile verification with trustPolicy on Linux. In one 1,800-entry workspace, a lockfile update now peaks at 1.8 to 2.0 GB. It peaked at 2.6 to 3.7 GB before #17020.
pnpm install in a Cargo workspace skips crates that an earlier install already unpacked into the store. Before, a repeat install processed every crate in Cargo.lock again. pnpm install --force unpacks every crate again pnpm/tasks#69.
Concurrent installs that import the same package into one project now all complete. One of them used to fail with ENOTEMPTY when its copy of the package collided with the copy another install had already placed pnpm/tasks#48.
pnpm install now succeeds when node_modules is a symlink to an existing directory. Dependency hoisting previously rejected a symlinked node_modules as an invalid destination #17157.
A filtered first install under the isolated linker now links every workspace project by name into node_modules/.pnpm/node_modules, not only the selected ones pnpm/tasks#155.
With nodeLinker: hoisted, a filtered install such as pnpm --filter app add <pkg> keeps the root node_modules links and bins of the workspace projects it did not select. A project with no dependencies of its own lost them until the next full install.
pnpm install --filter with nodeLinker: hoisted and --prod or --dev now preserves previously installed dependency groups for unselected workspace projects pnpm/tasks#164. Repeat filtered installs also re-resolve when a transitive injected workspace dependency or a linked dependency's version changes.
With sharedWorkspaceLockfile: false, pnpm install now runs the workspace root's pnpmfile for every project, after the project's own pnpmfile. Before, it ran only the pnpmfile in the project's directory.
pnpm install and pnpm peers check now detect peer dependency issues and report linked package versions in linked projects that use package.json5 or package.yaml pnpm/tasks#172.
pnpm install and pnpm peers check no longer report an unmet peer when a workspace package's peer is provided by a remote tarball URL. pnpm now compares the peer range with the version in the tarball's manifest #17037.
pnpm prune now removes extraneous direct packages from node_modules when package.json and pnpm-lock.yaml are already in sync. pnpm prune also honors --filter, --recursive, sharedWorkspaceLockfile: false, and the trustLockfile setting and --trust-lockfile flag. With the lockfile trusted, pnpm prune --prod works offline when every package is in the store #16999.
pnpm install --frozen-lockfile now fails with ERR_PNPM_OUTDATED_LOCKFILE when a local directory dependency or injected workspace package changes a dependency to a different tarball URL or git commit #17129. It also fails when an injected workspace package changes a dependency's named-registry range, such as work:^2.0.0, to one the locked version no longer satisfies.
pnpm install --frozen-lockfile now accepts the lockfile it wrote for a file: dependency on a directory without a package.json. It also accepts the lockfile for an injected workspace package that bundles a dependency in bundledDependencies, lists a dependency in both dependencies and optionalDependencies, or publishes from a publishConfig.directory whose package.json lists other dependencies than the project's own. Before, these failed with ERR_PNPM_OUTDATED_LOCKFILE.
The lockfile now records a catalog: peer dependency of an injected workspace package as written in its package.json. It recorded the catalog's range before, so editing the catalog changed the consumer's lockfile entry pnpm/tasks#153.
pnpm install now resolves a git, tarball, or tag dependency of an injected workspace package again when its spec changes. Before, it kept the old version.
Repeat installs and verifyDepsBeforeRun now re-check projects that inject a modified workspace package, including when sharedWorkspaceLockfile is false #17007, and accept aliased workspace: ranges on linked dependencies.
An injected workspace package that was linked now becomes a copy when the project that depends on it starts providing one of its peers at a version the package's own workspace context lacks. The link used to stay until that dependency was updated, so the package could not find the peer the project provides #17057.
An injected workspace package now keeps only the files its manifest lists after a lifecycle script or a script named in syncInjectedDepsAfterScripts rebuilds it. Before, these refreshes copied every file of the package directory into the injected copy, including files that files or .npmignore leave out. With deployAllFiles: true the copy still gets every file.
A script listed in syncInjectedDepsAfterScripts now keeps a package's links to its own files as links in the injected copies, the way pnpm install writes them, and updates those copies when sharedWorkspaceLockfile is false. Before, a directory link the script added became a real directory or went missing with deployAllFiles, and with sharedWorkspaceLockfile: false the copies kept the files from the last install.
Pressing Ctrl+C during pnpm -r run or pnpm --filter <pkg> run no longer reports ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL. pnpm now ends with the interrupted script's status, such as 130 for a script that SIGINT ended on Linux or macOS #16964.
With enableGlobalVirtualStore, a Node.js resolve hook that a script registers now sees the importer as context.parentURL after pnpm's NODE_PATH fallback fails to find a bare specifier. Hooks that resolve tsconfig paths aliases from the importer failed with ERR_MODULE_NOT_FOUND #16979.
pnpm run, pnpm exec, and pnpm restart now pass the install flags they were given, such as --lockfile-dir, --modules-dir, --store-dir, --offline, and --ignore-scripts, to the pnpm install that verifyDepsBeforeRun: install starts. When that install leaves the dependencies out of date, pnpm now prints a warning.
A repeated pnpm install --filter now finishes without reinstalling when the selected projects are up to date, and so does pnpm install once filtered commands have installed every project. After a filtered install, pnpm run and pnpm exec now install a selected project whose dependencies changed in between #17011, require the workspace root when a filtered install with pruneDirectDependencies: true skipped it pnpm/tasks#181, and preserve the recorded ignored build scripts of unselected projects.
The check that runs before a script now holds the workspace projects that the selected project depends on, including with sharedWorkspaceLockfile: false and for workspace dependencies declared with link:. --filter=<project>... now selects link: dependencies as well. In a workspace that has no package.json at its root, pnpm run and pnpm exec no longer reinstall before every command when the dependencies are up to date.
verifyDepsBeforeRun and repeat pnpm install runs now apply overrides before comparing a modified package.json with pnpm-lock.yaml #17127. pnpm install with optimisticRepeatInstall now re-runs when configDependencies changed, verifyDepsBeforeRun reports node_modules out of date when useGitBranchLockfile is enabled and the branch lockfile is missing, and in a single-project repository both checks record a successful lockfile check so later runs skip it until the lockfile changes #16993.
pnpm install and verifyDepsBeforeRun now compare manifests, lockfiles, and patch files by content hash. They notice an edit that kept the file's modification time, as cp -p, rsync -a, or an archive extraction leave it, and a patch file that was copied or touched without changing its content no longer marks dependencies as outdated #16988.
pnpm deploy now deploys file: dependencies that live outside the workspace directory. It failed with "Refusing to deploy unsafe lockfile path" #16983.
pnpm deploy now records the peer dependencies of the workspace packages it copies into the deployed lockfile. Before, pnpm rejected that lockfile with --frozen-lockfile when a deployed workspace package declared a peer and injectWorkspacePackages was off #17093.
pnpm install --frozen-lockfile and verifyDepsBeforeRun now succeed inside a directory created by pnpm deploy. pnpm deploy writes self-contained workspace and lockfile settings, prunes unused patchedDependencies, and preserves workspace-level dependency resolutions on deployed directory dependencies.
On macOS, pnpm deploy no longer writes a second, unused copy of every package to node_modules/.pnpm/@ in the deploy directory #17116.
pnpm patch-commit and pnpm install now apply a patch that renames or moves a file of the patched package. Such a patch failed with "rename/copy operations in patches are not yet supported".
In workspaces with sharedWorkspaceLockfile: false, pnpm patch, pnpm patch-commit, and pnpm patch-remove now resolve patch files and patchedDependencies entries at the workspace root. pnpm install checks configured patches across all workspace projects before reporting unused patches.
pnpm pack and pnpm publish no longer include editor swap files such as .*.swp, macOS ._* files, .lock-wscript, .wafpickle-*, build/config.gypi, or archived-packages/ in the tarball. Naming one of these files in files still includes it #16955.
pnpm pack and pnpm publish now support extended glob patterns and brace ranges such as part{1..3}.js and part{a..c}.js, including descending ranges, steps, and zero padding, in files, .npmignore, and .gitignore. Explicitly listed internal directory symlinks are preserved below excluded directories, entry points honor nested ignore files, ignore negations can re-include default-excluded logs and backup files, and nested lockfiles follow the package's file selection rules.
Trusted publishing with OIDC now works with registries whose URL has a path, such as https://registry.example/npm/private/. pnpm previously sent the token exchange request to the root of the registry host.
pnpm deprecate and pnpm unpublish now work for packages whose registry metadata is larger than 10 MiB, such as typescript. They accept up to 50 MiB, the same limit as pnpm owner.
pnpm owner ls now lists the owners of a package on the npm registry. It reported every package as not found.
pnpm licenses list --prod now includes optional dependencies, including transitive ones. Pass --no-optional to leave them out. pnpm licenses list also reports no licenses for workspace projects not recorded in the lockfile, errors when pnpm-lock.yaml is missing, and formats empty results as the requested text or JSON pnpm/tasks#174.
pnpm why now reads each selected workspace project's lockfile and modules directory when sharedWorkspaceLockfile is false pnpm/tasks#169.
pnpm pkg fix now converts a repository string such as github:pnpm/example to the object form, as npm pkg fix does. It also normalizes a GitHub, GitLab, or Bitbucket repository URL the way npm pkg fix does #16980.
Registry credentials and TLS settings passed with --config, such as --config.//registry.example.com/:_authToken=<token>, are now applied. They take precedence over the same settings in .npmrc files.
pnpm now reads only the settings it needs to decide whether to switch to the pnpm version a project pins. A setting outside them can no longer fail that decision or change its outcome. For example, pnpm --version no longer fails in a pinned project whose pnpm-workspace.yaml has a setting this pnpm cannot read. Projects that pin neither pnpm nor a runtime skip this check without reading any settings.
When pnpm switches to the version a project pins, an option only the pinned pnpm knows now reaches that pnpm when it comes immediately before the command name, as in pnpm --new-flag install. When switching for pnpm --version or an unrecognized command line, pnpm also honors --color, --no-color, --reporter, and --loglevel wherever they appear on the command line.
pnpm self-update now updates the project's pnpm pin when Homebrew installed pnpm or Corepack runs it, leaving the global pnpm alone #17001. Run inside a workspace package, pnpm self-update updates the pin in the workspace root's manifest, including in package.yaml or package.json5.
pnpm setup now completes when Windows registry environment values cannot be read or written. It prints PowerShell commands to configure PNPM_HOME and PATH without registry access #17167.
pnpm setup now succeeds when it cannot tell which shell configuration file to update, for example in a container where SHELL is not set. It installs pnpm and prints the PNPM_HOME and PATH lines to add yourself. Previously it failed with ERR_PNPM_UNKNOWN_SHELL, and so did the installer script at get.pnpm.io #16973.
In StackBlitz WebContainers, pnpm no longer crashes intermittently with Parking not supported on this platform, and running a command that does not exist now reports that the command was not found. Previously it sometimes failed with a generic error.
This release adds the sideEffectsCache.exclude setting, stops pnpm install from waiting on the daily update check, and keeps pnpm from aborting with a
This release adds the sideEffectsCache.exclude setting, stops pnpm install from waiting on the daily update check, and keeps pnpm from aborting with a core dump when the reader of its output exits.
Added the sideEffectsCache.exclude setting for packages whose build depends on something pnpm cannot include in the cache key, such as the system libraries a native addon links against. pnpm builds the listed packages in every project and never restores or saves their builds through the side-effects cache, locally or on a remoteCache server. Under the global virtual store, each project gets its own copy of these packages and of the packages that depend on them. Entries use the same name, @scope/*, and name@version patterns as minimumReleaseAgeExclude #5271.
pnpm login now prints the npm-notice response header during web-based login. Registries use it to show the verification code that completes the sign-in in the browser.
pnpm install and pnpm add no longer wait for the daily update check. If the command finishes first, pnpm skips the update notice and checks again next time. On a registry that accepted the connection but never answered, an install that had nothing to do used to take minutes #16839.
pnpm install, pnpm add and pnpm update now reuse pnpm-lock.yaml when the workspace configures a catalog entry that no dependency references, such as an unused entry or one whose package an overrides entry replaces. Before, every resolution in such a workspace resolved all dependencies again from the registry #16923.
pnpm install now looks up a git dependency's branch or tag once per install, even when many workspace projects depend on it. With linkWorkspacePackages enabled, it used to run git ls-remote once per project #16899.
A filtered install, such as pnpm install --filter <pkg>, now keeps the pnpm-lock.yaml entries of workspace projects that are missing from disk, as in a sparse checkout. Their importers, packages, and catalog entries stay even when the filter matches every project on disk #16931.
pnpm now decides whether a dependency that a package also declares as an optional peer is linked as a dependency or as a peer from the shallowest path that reaches the package. When an existing lockfile records such a dependency as a regular dependency and a newly added dependency now provides the peer, pnpm records it as a peer, as a fresh install does. The lockfile entry of such a package can change on the next install #16901.
An install that adds nothing to the store no longer changes the modification time of the store directory. CI caches that check modification times, such as GitLab's, no longer re-upload an unchanged store #16929.
pnpm no longer aborts with a core dump when the reader of its output has exited, as in pnpm list | head -1 or pnpm start 2>&1 | head -1. The command finishes with its usual exit code, and a failing script's exit code is kept. A write to stdout that fails for another reason, such as a full disk, ends the command with exit code 1 #16904 pnpm/tasks#132.
On Windows, pnpm exec, pnpm run, and commands such as pnpm nx now return when the command they run exits, even if it left a detached process running and pnpm's output is redirected or piped. Previously a shell reading that output waited until the detached process, such as the Nx daemon, exited #16930.
Commands that do not write the project manifest now leave a missing package.json absent. This covers queries such as pnpm why and pnpm outdated, pnpm fetch, pnpm dedupe --check, and commands that exit with an error, such as pnpm rt ls. These commands used to create one from the initialization template. pnpm sbom run from a lockfile alone now reports the root component as unknown with version 0.0.0 #16907.
pnpm run now reports a failed script as a JSON record under --reporter=ndjson. It printed a plain [ELIFECYCLE] line to stderr.
pnpm run no longer prints [ELIFECYCLE] Command failed with exit code N. to stderr when a script fails under --reporter=silent, --silent, or --loglevel=silent.
pnpm pipeline --dry-run no longer writes a run report when no projects are selected. With --json it prints {"tasks": []} pnpm/tasks#126.
pnpm pack and pnpm publish now ship the whole gitignored directory that main, browser, or bin points into, as npm does. Previously only the main and bin files themselves were packed, and a gitignored browser file was left out #16908.
pnpm pack and pnpm publish now honor a .npmignore or .gitignore inside a subdirectory when package.json has a files field. The package root's ignore files and those inherited from the workspace are still skipped #16909.
--registry, --https-proxy, --http-proxy, and --no-proxy now apply when pnpm resolves and downloads the pnpm version a project pins in packageManager. Before, these lookups went to https://registry.npmjs.org/, which a firewall that only allows a private registry blocks #16911.
On Windows, pnpm install now installs the Rust toolchain for rustup's default host, so a machine set up with rustup set default-host x86_64-pc-windows-gnu gets the MinGW toolchain. Without a default host, pnpm installs the MSVC toolchain for the machine's architecture, as rustup does. This includes a pnpm built for MinGW, such as the MSYS2 package, which has installed the MinGW toolchain since 12.13.0. An x64 pnpm on ARM64 Windows now installs the ARM64 toolchain #16854.
This release adds the pnpm profile and pnpm token commands, the storeIndexFormat: files setting for stores shared over a network filesystem, and faste
This release adds the pnpm profile and pnpm token commands, the storeIndexFormat: files setting for stores shared over a network filesystem, and faster Python dependency resolution.
Added the pnpm profile command to view and update registry user profile settings.
Added pnpm token to list, create, and revoke authentication tokens on the registry.
Added the storeIndexFormat setting. Set it to files to keep a store's package index as one file per package instead of the SQLite index.db, for a store on a network filesystem that several machines use at once. SQLite's locking does not work across machines, so concurrent installs on such a store could corrupt index.db.
Added the nodePackageMap setting, which groups the package-map settings. nodePackageMap.mode: write-only writes node_modules/.package-map.json for other tools without making Node.js load it. mode: load also makes Node.js load the map, like nodeExperimentalPackageMap: true. nodePackageMap.type replaces nodePackageMapType. The old settings still work #14937.
nodePackageMap:
mode: write-only
type: loosepnpm setup now works when pnpm was installed with npm on macOS. It installed pnpm from npm's bin directory and left a $PNPM_HOME/bin/pnpm that could not run #16855.
pnpm runs again after pnpm setup when globalShims enables pnpm. Every command failed with "the global target of the pnpm shim points back at the shim" #16874.
A pnpm built for the MinGW target on Windows, such as the MSYS2 package, now installs the MinGW Rust toolchain that rust-toolchain.toml names. It used to install the MSVC toolchain.
On macOS, pnpm install no longer fails with ERR_PNPM_LOCKFILE_WRITE_FILE when the project is on a virtiofs or SMB share. pnpm now falls back to a regular fsync when the file system rejects a full sync #16846.
On macOS, pnpm install, pnpm patch-commit, and other commands that load a pnpmfile no longer hang at random.
pnpm install now puts the executables of a Python build backend's requirements on the PATH while the backend runs. Projects built with uv_build now install. Before, they failed with "uv-build was not properly installed".
Removing a link: dependency now also removes its symlink from node_modules when nodeLinker is hoisted #16884.
pnpm-lock.yaml no longer records the tarball URL of a package installed from a scoped registry, such as one set by @types:registry=, when pnpm can rebuild the URL from that registry #16866.
pnpm pack and pnpm publish now pack only package.json, the README, the license, and the files named in main and bin when files is an empty array. They used to pack every file in the package #16889.
pnpm audit and pnpm audit signatures no longer check runtimes installed through devEngines.runtime, such as node@runtime:24.21.0, against the npm package of the same name. pnpm audit signatures reported these runtimes as having an invalid registry signature #16869.
pnpm pipeline now runs the root's tasks when pnpm-workspace.yaml lists only the root in packages or omits packages, as pnpm -r run does. A change to a root file in such a workspace no longer triggers a full-run warning. When a full run has no projects to run, pnpm pipeline now reports that no projects are selected #16849.
pnpm install resolves Python dependencies faster. With --lockfile-only, a project with 10 dependencies now resolves in about 4 seconds, down from about 40. When the index publishes a metadata file beside each wheel (PEP 658), as PyPI does, pnpm downloads only the wheels of the releases it selects.
A repeat install against an existing lockfile no longer reads registry metadata for the dependencies it takes from that lockfile. On a warm store this removes thousands of metadata lookups from a repeat install of a large workspace.
pnpm install with enableModulesDir: false now verifies the packages already in the store while the dependencies resolve, and checks a package's files in parallel. On a 5,100-package install with the store on a network filesystem, this removed a 19-second pause between resolution and fetching.
This release adds OIDC authentication to pnpm dist-tag and the tool: protocol. pnpm publish now checks which registry an NPM_ID_TOKEN was issued for b
This release adds OIDC authentication to pnpm dist-tag and the tool: protocol. pnpm publish now checks which registry an NPM_ID_TOKEN was issued for before using it.
pnpm publish now uses an NPM_ID_TOKEN only if its aud claim matches the selected registry, such as npm:registry.npmjs.org. A token for another registry is skipped with a warning, and pnpm falls back to the configured credentials.
pnpm dist-tag add, rm, and ls now support OIDC authentication in CI. Enable "Allow npm dist-tag" in the package's trusted publishing settings to manage tags without a stored npm token.
Added the tool: protocol for the tools pnpm downloads itself: Node.js, Bun, Deno, and Yarn. pnpm add bun@tool:1.3.0, pnx node@tool:22, and pnx yarn@tool:4 work like the runtime: spelling, which stays supported as an alias. A lockfile written for runtime: stays up to date when package.json switches to tool:, and the other way around.
A named registry can no longer be called tool.
This release shares task results and dependency builds through a remote cache, adds the addMissingPeerTypes setting, and lets pnpm add --config and pn
This release shares task results and dependency builds through a remote cache, adds the addMissingPeerTypes setting, and lets pnpm add --config and pnpm update manage configuration dependencies. It also fixes dangerouslyAllowAllBuilds running the build scripts of packages that allowBuilds denies.
pnpm pipeline can share task results between machines. A result is a signed artifact stored on a pnpr server or on a server that speaks the Turborepo Remote Cache API, such as Vercel Remote Cache.
The remote side-effects cache can also store dependency builds on a Turborepo Remote Cache server. Both caches read the new remoteCache setting, which names the server and holds the signing keys. pnpm pipeline --report records the run under the organization remoteCache.org names.
Added the addMissingPeerTypes setting, which links the @types package of a peer dependency next to every package that peer-depends on it. For example, a package that peer-depends on react gets the project's @types/react linked next to it. This lets TypeScript find the types of a peer dependency when the global virtual store is on #15689.
pnpm add --config and pnpm update now handle configuration dependencies the way they handle other dependencies #16814.
pnpm add --config saves a version range in pnpm-workspace.yaml by the same rules as pnpm add, so pnpm add --config my-config@latest saves a range such as ^1.2.0. It also resolves the package again when pnpm-lock.yaml already locks an older version.
pnpm update updates configuration dependencies within their ranges, and pnpm update --latest moves them to their latest version. A selector such as pnpm update my-config updates only the configuration dependencies it names.
A package set to false in allowBuilds no longer runs its build scripts when dangerouslyAllowAllBuilds is true. The two settings together now allow every build except the denied ones. Previously, dangerouslyAllowAllBuilds ignored the denials.
pnpm now switches to the pnpm version a project pins even when it cannot read its configuration. Previously, a setting it rejected in the global config file, an .npmrc file, or _auth, or a pnpm-workspace.yaml it could not parse, stopped every command, pnpm --version included.
pnpm update and pnpm why accept --depth Infinity again. They failed with invalid value 'Infinity' for '--depth <DEPTH>' #16817.
pnpm deploy without injectWorkspacePackages now binds a peer dependency of a linked workspace package to the version its parent provides, as an injected install does. Previously the deploy failed with ERR_PNPM_DEPLOY_AMBIGUOUS_PEER whenever other packages in the deployed graph depended on different versions of that peer #16807.
pnpm deploy --legacy no longer fails with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER when a workspace dependency of the deployed project declares a workspace: peer dependency that the project does not depend on itself. pnpm now copies that peer from the workspace into the deploy directory.
An auto-installed peer declared with workspace: now always resolves to the workspace project. Previously, workspace:* and workspace:^1.0.0 peers could be installed from the registry #16806.
Repeat installs no longer resolve again when an injected workspace package lists a dependency also as a peer dependency.
Sped up frozen installs of unchanged injected workspace packages that use hardlinks.
Sped up workspace discovery with subtree exclusions such as !generated/**.
A key under a registry URL in the _auth setting that does not start with @ is now skipped with a warning, so a field a later pnpm version adds there no longer breaks this one. A key that holds an authToken object but lacks its @, such as org for @org, is still an error.
This release fixes --workspace-concurrency=Infinity , filters set by an updateConfig hook, and store fetches with enable-modules-dir=false .
This release fixes --workspace-concurrency=Infinity, filters set by an updateConfig hook, and store fetches with enable-modules-dir=false.
--workspace-concurrency=Infinity now runs workspace projects with no concurrency limit. It used to fail with invalid digit found in string #16793.
pnpm install and other recursive commands now apply the filter and filterProd that an updateConfig hook sets. They used to run on every workspace project #16792.
enable-modules-dir=false now also fetches the packages an install reuses from an existing lockfile, so the store holds every package the lockfile lists.
This release fixes two ways pnpm install could fail, runs tools of any Rust release through pnx , and treats registry.npmjs.com as an alias of the npm
This release fixes two ways pnpm install could fail, runs tools of any Rust release through pnx, and treats registry.npmjs.com as an alias of the npm registry.
pnpm install no longer fails when packageManager pins the pnpm version that is already running and the registry does not publish that version. pnpm warns and continues. A registry mirror that has not synced a release no longer blocks the commands of a project pinned to it.
pnpm install no longer fails with ERR_PNPM_CMD_SHIM_CHMOD when node_modules/.bin holds a shim that another user created, if everyone can already execute it and it is not world-writable. This happens when several users share one checkout.
enable-modules-dir=false (enableModulesDir: false through the Node.js addon) fetches the registry packages the host can install into the store again, as pnpm v10 did, while still writing nothing under node_modules. The setting exists for a node_modules that something else mounts from the store, such as a FUSE daemon, and that consumer no longer has to download each package on first access. A plain --lockfile-only run still fetches nothing.
pnpm pack and pnpm publish no longer put .npmignore and .gitignore files in the tarball. A files entry that names one still ships it.
pnpm now treats https://registry.npmjs.com/ as an alias of https://registry.npmjs.org/. Registry requests, credentials, and trusted publishing use the canonical hostname.
pnx --package=rust@<channel> <tool> runs a tool of that Rust release, for example pnx --package=rust@nightly-2026-01-01 cargo build. pnpm installs the release with the components and targets from rust-toolchain.toml and the target of each --target argument.
pnpm install now links agent skills for more coding agents. It detects the agent from ANTIGRAVITY_AGENT, COPILOT_AGENT, COPILOT_CLI, CODEX_THREAD_ID, CODEX_SANDBOX, AI_AGENT, and CLAUDE_CODE pnpm/tasks#116.
When the registry rejects pnpm stage publish, the error message now starts with "Failed to stage package".
pnpm audit --fix update now updates only the dependencies whose locked version is vulnerable #14928 .
This release adds Rust toolchain management, links the agent skills that dependencies ship, adds the permissions setting, and keeps the colors of streamed script output.
pnpm install now links the agent skills that direct dependencies ship under skills/<name>/SKILL.md into the project's agent skill directories, such as .claude/skills. A package's skills are linked only after you approve them with pnpm approve. The skills.dirs setting chooses the directories pnpm/rfcs#35.
Added the permissions setting, which records what each dependency may do. Its build capability works like allowBuilds and takes precedence over it. pnpm approve-builds writes to permissions when pnpm-workspace.yaml already has it, and to allowBuilds otherwise.
Added pnpm permissions, which lists the granted and denied permissions and the packages awaiting approval. pnpm approve reviews build scripts and agent skills in one prompt pnpm/rfcs#36.
pnpm now installs and runs Rust toolchains.
cargo.enabled, pnpm install installs the toolchain named in rust-toolchain.toml. pnpm verifies the release signature, stores the toolchain once per machine, and links it into .pnpm/rust. pnpm run and pnpm exec put its cargo and rustc on the PATH.pnpm add -g rust@<channel> installs a toolchain globally. The cargo and rustc commands run it outside projects that pin their own. pnpm update -g, pnpm ls -g, and pnpm remove -g manage it like any global package.pnpm add rust@<channel> pins the toolchain in rust-toolchain.toml.pnpm shim add rust adds project-aware shims for cargo, rustc, and the other Rust tools. In a project with a rust-toolchain.toml, they run the toolchain the file names and install it on first use. Elsewhere, the next command of the same name on PATH runs, such as rustup's.pnpm run and pnpm exec now keep the colors of script output that they print under the project's name, such as with --stream. pnpm sets FORCE_COLOR=1 for these scripts when its own output is in color, unless FORCE_COLOR is already set.
Script output is also rendered more cleanly:
\r shows only its last state.pnpm -r run no longer garbles its live output when a script fails while other scripts are still running.pnpm no longer panics with "unexpected error when polling the I/O driver" when it runs under QEMU user-mode emulation, such as a linux/amd64 container on an Apple Silicon Mac #16696.
pnpm view, pnpm update, and other commands that read registry metadata now work behind proxies that end a response by closing the connection without a TLS close_notify alert #16704.
pnpm now switches to the version a project pins in packageManager or devEngines.packageManager even when pnpm-workspace.yaml has a setting the running pnpm cannot read, such as a lockfile.includeResolutionSettings section. If pnpm does not switch, it still reports that setting #16675.
When the pnpm package has to download its native binary on first run, it now uses the registry and credentials from .npmrc and from the npm_config_registry and pnpm_config_registry environment variables. COREPACK_NPM_REGISTRY still takes precedence. A project .npmrc is not read when COREPACK_INTEGRITY_KEYS turns off the signature check #16655.
pnpm install and pnpm add --config now apply minimumReleaseAge when they resolve a config dependency. A config dependency range resolves to the newest version that is old enough, so a later clean pnpm install --frozen-lockfile accepts the lockfile #16660.
pnpm remove with catalogPrune no longer removes catalog entries that pnpm-lock.yaml still records for workspace projects missing from disk. Before, a following frozen install failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH #16679.
With cargo.enabled, pnpm install now writes the source replacement for vendored crates into .pnpm/crates/config.toml and includes it as optional from .cargo/config.toml. A checkout without .pnpm builds with plain Cargo #16659.
With nodeLinker.type set to loaded, Node.js now stops with ERR_PNPM_LOADER_UNSUPPORTED_NODE when it preloads the store loader on a version the loader cannot serve. The supported versions are ^24.18.0 || >=26.2.0. On other versions, CommonJS packages imported from ESM failed with Cannot find module on their first relative require().
On Windows, pnpm install no longer fails with "The filename, directory name, or volume label syntax is incorrect" when a package contains a file whose name is invalid on Windows, such as icon.svg?as=metadata.d.ts. pnpm removes the invalid characters from the name and prints a warning that lists the renamed files.
On Windows, hoisting no longer fails intermittently with link errors when a junction is created or replaced concurrently pnpm/tasks#53.
pnpm install --no-optional now installs the peer dependencies a project declares when autoInstallPeers is on. The lockfile marked such a peer optional: true when another dependency had it as an optional peer.
pnpm install and pnpm dedupe now link an optional peer to the workspace package that the workspace root depends on when the picked version matches it. They installed the registry package with the same name and version #16706.
Removal overrides such as "debug>supports-color": "-" now also apply to an optional peer that a package declares only in peerDependenciesMeta #16681.
pnpm add and other installs that re-resolve dependencies now keep the locked devEngines.runtime version while it still satisfies the declared range #16764.
pnpm audit --fix update now updates only the dependencies whose locked version is vulnerable #14928.
pnpm outdated and pnpm update --interactive now apply overrides before they look up the latest version. Before, a dependency overridden to an npm alias was compared with the latest version of the package the override replaces #16719.
Patches saved with CRLF line endings now apply, including a patch that creates or deletes a file. pnpm rejected the git headers of such a patch with ERR_PNPM_INVALID_PATCH and the message invalid file mode: 100644 #16641.
A patch that changes a file's mode, such as adding or removing the executable bit, now applies the new mode on Unix pnpm/tasks#110.
With sharedWorkspaceLockfile: false, an injected workspace package installed in the same run as its dependent now holds only the files its files field selects. The copy also held other files of the project, such as tsconfig.json #16683.
A script listed in syncInjectedDepsAfterScripts no longer fails when it rewrites package.json while pnpm is copying its edits into the injected copies. The sync after the script now replaces a half-copied manifest.
pnpm deploy with a shared lockfile no longer fails with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH for settings.dedupeInjectedDeps or settings.dedupePeerDependents when lockfile.includeResolutionSettings is enabled. The deployed lockfile now records both settings as false, the values the deploy installs with.
pnpm deploy now writes the dependencies in the deployed package.json sorted by name. It also sorts the allowBuilds entries in the deployed pnpm-workspace.yaml. Repeated deploys of the same lockfile now produce identical files #16687.
pnpm pack and pnpm publish now match .npmignore and .gitignore rules the way npm does. A negation such as !lib/** or !lib/**/!(*.map) re-includes files under a directory that an earlier * rule excluded #16743.
pnpm pack and pnpm publish no longer always include root files that merely start with README, LICENSE, or LICENCE, such as README_INTERNAL.md. Only README, LICENSE, LICENCE, and COPYING, with or without an extension, ship regardless of files and .npmignore, as in npm #16753.
pnpm publish --provenance=false and --no-provenance now turn off provenance under trusted publishing, so a package can be published from a self-hosted runner. Setting provenance: false in pnpm-workspace.yaml does the same #16721.
pnpm install hardlinks files from a group-writable or world-writable store again. pnpm copied every file from such a store into node_modules #16677.
A repeat pnpm install no longer imports patched packages and packages with build scripts again when nothing changed. Their builds no longer run again either. This happened when recursiveInstall was false or the project had a file: dependency #16705.
Verifying the lockfile against trustPolicy and minimumReleaseAge uses less memory. pnpm no longer keeps every published version's manifest of each checked package in memory until the install ends #16656.
pnpm rebuild <pkg> and pnpm rebuild --pending no longer read the manifest of every installed package to find build scripts. Only the selected packages are inspected and built. On a large node_modules served lazily, such as over a network or FUSE mount, this turned a rebuild of a few packages into a fetch of every package.
pnpm rebuild no longer removes and recreates node_modules when the settings recorded in node_modules/.modules.yaml differ from the current configuration. The rebuild runs the build scripts against the installed packages as they are.
pnpm store prune now compacts the store's index.db after removing package entries, so the file shrinks again #16717.
pnpm whoami, pnpm bugs, pnpm docs, pnpm repo, pnpm star, pnpm unstar, and pnpm stars now honor the --registry option.
--registry now takes precedence over a scope's configured registry for scoped packages in pnpm access, pnpm view, pnpm repo, pnpm star, pnpm unstar, pnpm owner, pnpm deprecate, pnpm undeprecate, pnpm unpublish, pnpm dist-tag, pnpm team, and pnpm stage. Without --registry, pnpm access now sends a scoped package or scope to the registry configured for that scope.
Registry commands now keep the path of a registry URL such as https://example.com/npm/ when they build request URLs. This applies to pnpm access, pnpm owner, pnpm ping, pnpm search, pnpm star, pnpm stars, pnpm team, pnpm unstar, and pnpm whoami.
pnpm view now honors the network retry settings.
pnpm repo now fetches the repository URLs of several packages in parallel.
pnpm install --fix-lockfile no longer removes the deprecated and hasBin fields from lockfile entries #6600 .
This release fixes pnpm install failures after an overrides change and on a filtered frozen install with catalogPrune. It also fixes several bugs in the experimental nodeLinker.type: loaded, which now keeps its generated files in node_modules.
With nodeLinker.type: loaded, pnpm now writes its generated files to node_modules, which projects already ignore in git. The store manifest and loader are node_modules/.pnpm/.store-manifest.json and node_modules/.pnpm/.store-loader.mjs. Bin shims are in node_modules/.bin.
Earlier versions wrote .pnpm-store.json and .pnpm-store-loader.mjs to the project root, and a .pnpm directory to the root and to each workspace package. Delete them after reinstalling.
With nodeLinker.type: loaded, packages that ship their own node_modules directory, such as npm with its bundled dependencies, now load from the store. Before, one such package in the install stopped every Node.js process from starting.
With nodeLinker.type: loaded, scripts can now run a Node.js runtime installed through devEngines.runtime. Before, every script that called node re-ran its own shim until it failed with "Argument list too long".
With nodeLinker.type: loaded, Node.js processes start faster. In a project with 13,000 stored files, the startup overhead per process dropped from 67 ms to 18 ms.
pnpm install no longer fails with ERR_PNPM_NO_MATCHING_VERSION after a change to overrides when the lockfile resolves an optional peer dependency to an npm alias of another package #16654.
A frozen install with catalogPrune no longer removes catalog entries that pnpm-lock.yaml still records. Before, pnpm install --frozen-lockfile --filter failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH when some workspace projects were missing from disk #16638.
pnpm install --fix-lockfile no longer removes the deprecated and hasBin fields from lockfile entries #6600.
With enableGlobalVirtualStore, an install that updates node_modules now repairs a package in the global virtual store that an interrupted install left without some of its dependency links or package files. Before, such an install kept the incomplete package if the project's node_modules already recorded it #16642.
pnpm install now skips the Cargo and Python projects inside a nested directory that has its own pnpm-workspace.yaml or .git directory, such as a git worktree of the same workspace or a separate clone.
The Request took warning for package metadata now starts timing when pnpm sends the request. Before, it also counted the time the request waited for a free request slot, so large installs printed it for requests the registry answered quickly.
One column per quarter.