@pnpm/exe 12.3.1 → 12.3.2

package/bin/pnpm.mjs

@@ -3,17 +3,14 @@
 // `./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
-// ordinary `npm install -g pnpm` never pays for a Node.js startup:
-// `package.json#bin` points at the native binary.
+// Only Corepack reaches this file: `package.json#bin` still points at the native
+// binary, so an ordinary `npm install -g pnpm` never pays for a Node.js startup.
 //
 // Corepack installs no dependencies and runs no lifecycle scripts, so the
 // `@pnpm/exe.<target>` package that carries the binary is absent and
 // `install.js` never ran. The binary is therefore downloaded on first use and
 // kept next to this wrapper — where the native binary also finds the `dist/`
-// payload it ships node-gyp in. The placeholder's installs usually do carry
-// that package, and the binary is taken from there.
+// payload it ships node-gyp in.
 //
 // The download itself is `get-pnpm`, the package behind https://get.pnpm.io,
 // which already knows how to verify one; it travels in that same `dist/`

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

@@ -1,9 +1,9 @@
 {
-  "lastValidatedTimestamp": 1788394737104,
+  "lastValidatedTimestamp": 1788478744905,
   "projects": {
     "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy": {
       "name": "pacquet",
-      "version": "12.3.1"
+      "version": "12.3.2"
     }
   },
   "pnpmfiles": [],

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 pnpm
+// cannot run.
 //
 // `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.2",
   "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.2",
+    "@pnpm/exe.win32-arm64": "12.3.2",
+    "@pnpm/exe.darwin-x64": "12.3.2",
+    "@pnpm/exe.darwin-arm64": "12.3.2",
+    "@pnpm/exe.linux-x64": "12.3.2",
+    "@pnpm/exe.linux-arm64": "12.3.2",
+    "@pnpm/exe.linux-x64-musl": "12.3.2",
+    "@pnpm/exe.linux-arm64-musl": "12.3.2"
   },
   "scripts": {
     "preinstall": "node install.js",

package/pnpm

@@ -1,21 +1,4 @@
-#!/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'
-
-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'
-  )
-}
-
-await import('./bin/pnpm.mjs')
+This is a placeholder. pnpm's native binary replaces this file during
+installation (see ./install.js). If you are reading this, the install/build
+script did not run — reinstall with build scripts enabled (e.g. allow-list
+pnpm's build under pnpm or Bun, or drop --ignore-scripts).