pnpm 12.3.1 → 12.3.3

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # pnpm
 
+## 12.3.3
+
+### Patch Changes
+
+- Fixed concurrent installs sharing a store occasionally failing with an ENOENT error while importing a package file [#14353](https://github.com/pnpm/pnpm/issues/14353).
+
+- Sped up writing the lockfile in large workspaces [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- Sped up dependency resolution in large workspaces [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- pnpm now runs through Node.js when it was installed by a tool that skips build scripts, such as Vercel's `packageManager` provisioning, Bun, Deno, or `npm install --ignore-scripts`. Those installs previously failed with `syntax error near unexpected token ')'`. They still cannot run pnpm on Windows. On macOS only a shell can start it [#14346](https://github.com/pnpm/pnpm/issues/14346).
+
+## 12.3.2
+
+### Patch Changes
+
+- `pnpm audit --fix update` no longer aborts when a vulnerable package has no safe version inside its declared range [#14508](https://github.com/pnpm/pnpm/issues/14508). The run updates every package it can and lists the rest as remaining.
+
+- `pnpm install` no longer reruns root lifecycle scripts when the global virtual store contains an unfinished-build marker in a package slot that the current lockfile does not use [pnpm/pnpm#14485](https://github.com/pnpm/pnpm/issues/14485).
+
+- Sped up installs that have no lockfile. pnpm now links packages whose dependency subtree has no peer dependencies into the virtual store while resolution is still running.
+
+- `pnpm run` and `pnpm exec` now start without reinstalling on filesystems that keep sub-millisecond mtimes, such as NTFS. Previously, every run on those filesystems reinstalled first [pnpm/pnpm#14486](https://github.com/pnpm/pnpm/issues/14486).
+
+- `pnpm import` now keeps the versions recorded in `package-lock.json`, `npm-shrinkwrap.json`, or `yarn.lock` when it generates `pnpm-lock.yaml`. A range in `package.json`, a catalog, or an override still decides which versions are eligible, and the recorded version is preferred among them. The generated lockfile previously could pin newer versions than the source lockfile [#14476](https://github.com/pnpm/pnpm/issues/14476).
+
+  `pnpm import` in a workspace now imports every workspace project into the shared lockfile. It previously imported only the project in the current directory.
+
+  `pnpm import` now fails with `ERR_PNPM_LOCKFILE_NOT_FOUND` when none of the three source lockfiles is present. It also fails with `ERR_PNPM_YARN_LOCKFILE_PARSE_FAILED` when it cannot parse `yarn.lock`. It previously generated a lockfile from scratch in both cases.
+
+  `pnpm import` always resolves locally. It warns when `--pnpr-server` or the `pnpr-server` setting is given and does not use the server.
+
+- Sped up installs in large workspaces. Discovering the workspace projects no longer enumerates every matched directory to learn which manifest files it holds [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- Sped up installs in large workspaces. The resolver and the peer pass allocate less for every dependency edge [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- `pnpm self-update`, `pnpm with`, and automatic package-manager version switching no longer wait through registry retry delays when a configured registry has no signatures and `registry.npmjs.org` is unavailable [#14483](https://github.com/pnpm/pnpm/issues/14483).
+
+- Sped up installs in large workspaces. Saving the lockfile is faster, and the install finishes without waiting for memory cleanup [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- `pnpm install` now relinks workspace packages when `publishConfig.linkDirectory` changes. Frozen installs report an outdated lockfile until it is regenerated [pnpm/pnpm#14488](https://github.com/pnpm/pnpm/issues/14488).
+
+- The pnpm npm wrapper keeps its placeholder shebang-less so pnpm 11 can install pnpm 12 through the version store. Wrapper installs must allow lifecycle scripts to install the native binary [#14502](https://github.com/pnpm/pnpm/issues/14502).
+
+- Sped up dependency resolution when there is no lockfile, and for the dependencies a lockfile does not cover.
+
+- Sped up installs in large workspaces. Workspace `link:` targets and importer ids are now derived from the paths' suffixes under the workspace root [#14352](https://github.com/pnpm/pnpm/issues/14352).
+
+- `pnpm install` now reports "Already up to date" when local tarball dependencies have not changed [#14495](https://github.com/pnpm/pnpm/issues/14495).
+
+- `pnpm update` now accepts `--ignore-scripts` and skips lifecycle scripts during the update [pnpm/pnpm#14512](https://github.com/pnpm/pnpm/issues/14512).
+
+- Sped up installs that restore a deleted `node_modules` from a warm global virtual store. pnpm no longer re-links packages that are already fully present in the global virtual store [#14510](https://github.com/pnpm/pnpm/issues/14510).
+
 ## 12.3.1
 
 ### Patch Changes

package/bin/pnpm.mjs

@@ -3,8 +3,8 @@
 // `./bin/pnpx.mjs` for every pnpm >=11 (see its `config.json`) and loads them
 // into its own Node.js process, which a native executable cannot be loaded into.
 //
-// The `pnpm` placeholder bin runs it too, when the install script that
-// replaces it with the native binary did not run (build scripts blocked). An
+// The `pnpm` placeholder bin runs it too, on Unix, when the install script that
+// replaces it with the native binary did not (build scripts blocked). An
 // ordinary `npm install -g pnpm` never pays for a Node.js startup:
 // `package.json#bin` points at the native binary.
 //

package/dist/node_modules/.pnpm-workspace-state-v1.json

@@ -1,9 +1,9 @@
 {
-  "lastValidatedTimestamp": 1788394737104,
+  "lastValidatedTimestamp": 1788518270048,
   "projects": {
     "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy": {
       "name": "pacquet",
-      "version": "12.3.1"
+      "version": "12.3.3"
     }
   },
   "pnpmfiles": [],
@@ -28,7 +28,7 @@
         "@commitlint/prompt-cli": "^21.2.2",
         "@cyclonedx/cyclonedx-library": "10.2.0",
         "@eslint/js": "^10.0.1",
-        "@inquirer/prompts": "^8.7.0",
+        "@inquirer/prompts": "^8.7.1",
         "@jest/globals": "30.4.1",
         "@npm/types": "^2.1.0",
         "@openpgp/web-stream-tools": "0.3.1",
@@ -227,7 +227,7 @@
         "semver-utils": "^1.1.4",
         "shlex": "^3.0.0",
         "shx": "^0.4.0",
-        "socks": "^2.8.9",
+        "socks": "^2.8.10",
         "sort-keys": "^6.0.1",
         "split-cmd": "^1.1.0",
         "split2": "^4.2.0",

package/install.js

@@ -1,12 +1,13 @@
 #!/usr/bin/env node
 // Preinstall for the pnpm v12 wrapper (shared verbatim by `pnpm` and
-// `@pnpm/exe`): replace the placeholder bins with the host's native binary so
-// `pnpm` runs directly, no Node startup per call. Package managers write bin
-// shims after preinstall, so the shims are made from the binary; where build
-// scripts are blocked (`--ignore-scripts`, the pnpm/Bun default) the
-// placeholder stays and runs pnpm through Node.js (see the `pnpm` file). npm
-// does not re-read the rewritten `bin` during the same install pass, so on a
-// global Windows install, postinstall asks it to relink.
+// `@pnpm/exe`): replace the shebang-less placeholder bins with the host's native
+// binary so `pnpm` runs directly, no Node startup per call. The placeholder must
+// stay shebang-less because pnpm 11 records its interpreter before installing
+// the native binary at the same path. npm's global Windows shims still target
+// the extensionless path after the `bin` rewrite, so postinstall asks npm to
+// regenerate them against `pnpm.exe`. When lifecycle scripts are blocked
+// (`--ignore-scripts`, pnpm/Bun default), the placeholder remains and runs pnpm
+// through Node.js wherever a shell reaches it (see the `pnpm` file).
 //
 // `pn`/`pnpx`/`pnx` are committed `#!/bin/sh` scripts on Unix (so only `pnpm` is
 // relinked); on Windows the native binary is hardlinked onto each and

package/package.json

@@ -9,7 +9,7 @@
       "./dist/node_modules/node-gyp/gyp/gyp"
     ]
   },
-  "version": "12.3.1",
+  "version": "12.3.3",
   "description": "Fast, disk space efficient package manager",
   "keywords": [
     "pnpm",
@@ -46,14 +46,14 @@
     "THIRD-PARTY-NOTICES.md"
   ],
   "optionalDependencies": {
-    "@pnpm/exe.win32-x64": "12.3.1",
-    "@pnpm/exe.win32-arm64": "12.3.1",
-    "@pnpm/exe.darwin-x64": "12.3.1",
-    "@pnpm/exe.darwin-arm64": "12.3.1",
-    "@pnpm/exe.linux-x64": "12.3.1",
-    "@pnpm/exe.linux-arm64": "12.3.1",
-    "@pnpm/exe.linux-x64-musl": "12.3.1",
-    "@pnpm/exe.linux-arm64-musl": "12.3.1"
+    "@pnpm/exe.win32-x64": "12.3.3",
+    "@pnpm/exe.win32-arm64": "12.3.3",
+    "@pnpm/exe.darwin-x64": "12.3.3",
+    "@pnpm/exe.darwin-arm64": "12.3.3",
+    "@pnpm/exe.linux-x64": "12.3.3",
+    "@pnpm/exe.linux-arm64": "12.3.3",
+    "@pnpm/exe.linux-x64-musl": "12.3.3",
+    "@pnpm/exe.linux-arm64-musl": "12.3.3"
   },
   "scripts": {
     "preinstall": "node install.js",

package/pnpm

@@ -1,21 +1,38 @@
-#!/usr/bin/env node
-// pnpm's native binary replaces this file during installation (see
-// ./install.js). If this is running, that install script did not — build
-// scripts were blocked (pnpm and Bun block them by default) or skipped
-// (`--ignore-scripts`) — so pnpm runs through Node.js instead: `bin/pnpm.mjs`
-// finds the installed binary, or downloads one, and spawns it.
-//
-// Package managers write bin shims after preinstall has had its chance to run,
-// so a shim made from this file's shebang exists only where the binary never
-// arrived. That is also why this file is left in place once it is running: a
-// binary put here under such a shim would be run through `node`.
-import process from 'node:process'
+# pnpm's native binary replaces this file during installation (see
+# ./install.js). Until then this hands over to ./bin/pnpm.mjs, which finds the
+# installed binary or downloads one and spawns it.
+#
+# Shebang-less on purpose, and therefore an `sh` script: a bin shim generated
+# from a shebang records that interpreter, and pnpm 11 generates the shim before
+# it puts the native binary at this path.
+#
+# Something has to retry this file under a shell, because the kernel answers
+# ENOEXEC for it. A bin shim and a shell both do, and so does glibc's `execvp`.
+# Apple's libc does not, so on macOS a program that spawns this path itself gets
+# ENOEXEC; Windows has neither and cannot reach it at all.
+if ! command -v node > /dev/null 2>&1; then
+  echo "pnpm's native binary was not installed, and there is no Node.js to run pnpm without it." >&2
+  echo "Reinstall pnpm with build scripts enabled (allow-list pnpm's build under pnpm or Bun, or drop --ignore-scripts)." >&2
+  exit 1
+fi
 
-if (process.stderr.isTTY) {
-  process.stderr.write(
-    'pnpm is running through Node.js because the script that installs its native binary was skipped. ' +
-    'Reinstall pnpm with its build scripts allowed to run the binary directly.\n'
-  )
-}
+if [ -t 2 ]; then
+  echo "pnpm is running through Node.js because the script that installs its native binary was skipped." >&2
+  echo "Reinstall pnpm with its build scripts allowed to run the binary directly." >&2
+fi
 
-await import('./bin/pnpm.mjs')
+# $0 is whatever shim or symlink pnpm was launched through; ./bin/pnpm.mjs is
+# found relative to this file. The hop cap matches the kernel's ELOOP limit, so
+# a cycle cannot hang the script.
+self=$0
+hops=0
+while [ -L "$self" ] && [ "$hops" -lt 40 ]; do
+  hops=$((hops + 1))
+  link=$(readlink "$self")
+  case $link in
+    /*) self=$link ;;
+    *) self=$(dirname "$self")/$link ;;
+  esac
+done
+
+exec node "$(dirname "$self")/bin/pnpm.mjs" "$@"