@pnpm/exe 11.13.1 → 11.15.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/pnpm.mjs +3955 -3302
- package/package.json +9 -9
- package/CHANGELOG.md +0 -94
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pnpm/exe",
|
|
3
|
-
"version": "11.
|
|
3
|
+
"version": "11.15.0",
|
|
4
4
|
"description": "Fast, disk space efficient package manager",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pnpm",
|
|
@@ -35,17 +35,17 @@
|
|
|
35
35
|
"detect-libc": "^2.1.2"
|
|
36
36
|
},
|
|
37
37
|
"optionalDependencies": {
|
|
38
|
-
"@pnpm/linux-arm64": "11.
|
|
39
|
-
"@pnpm/linux-x64": "11.
|
|
40
|
-
"@pnpm/linuxstatic-arm64": "11.
|
|
41
|
-
"@pnpm/linuxstatic-x64": "11.
|
|
42
|
-
"@pnpm/macos-arm64": "11.
|
|
43
|
-
"@pnpm/win-arm64": "11.
|
|
44
|
-
"@pnpm/win-x64": "11.
|
|
38
|
+
"@pnpm/linux-arm64": "11.15.0",
|
|
39
|
+
"@pnpm/linux-x64": "11.15.0",
|
|
40
|
+
"@pnpm/linuxstatic-arm64": "11.15.0",
|
|
41
|
+
"@pnpm/linuxstatic-x64": "11.15.0",
|
|
42
|
+
"@pnpm/macos-arm64": "11.15.0",
|
|
43
|
+
"@pnpm/win-arm64": "11.15.0",
|
|
44
|
+
"@pnpm/win-x64": "11.15.0"
|
|
45
45
|
},
|
|
46
46
|
"devDependencies": {
|
|
47
47
|
"@jest/globals": "30.4.1",
|
|
48
|
-
"@pnpm/exe": "11.
|
|
48
|
+
"@pnpm/exe": "11.15.0",
|
|
49
49
|
"@pnpm/jest-config": "1100.0.21",
|
|
50
50
|
"@zkochan/cmd-shim": "^9.0.6",
|
|
51
51
|
"execa": "npm:safe-execa@0.3.0"
|
package/CHANGELOG.md
DELETED
|
@@ -1,94 +0,0 @@
|
|
|
1
|
-
# @pnpm/exe
|
|
2
|
-
|
|
3
|
-
## 11.13.1
|
|
4
|
-
|
|
5
|
-
### Patch Changes
|
|
6
|
-
|
|
7
|
-
- Correct the `@pnpm/exe` repository and homepage metadata so npm links to its current source directory.
|
|
8
|
-
|
|
9
|
-
## 11.9.1
|
|
10
|
-
|
|
11
|
-
### Patch Changes
|
|
12
|
-
|
|
13
|
-
- 96da7c5: node-gyp's `gyp_main.py` and `gyp` entrypoints are now packed with the executable bit in the `pnpm` and `@pnpm/exe` tarballs. Without it, building native addons from source could fail with a permission error.
|
|
14
|
-
|
|
15
|
-
## 11.6.1
|
|
16
|
-
|
|
17
|
-
### Patch Changes
|
|
18
|
-
|
|
19
|
-
- cd8348c: Updated `@zkochan/cmd-shim` to v9.0.6.
|
|
20
|
-
|
|
21
|
-
## 11.0.7
|
|
22
|
-
|
|
23
|
-
### Patch Changes
|
|
24
|
-
|
|
25
|
-
- fbeee82: Restore the execute bit on the `node-gyp` shims packed inside `@pnpm/exe` (`dist/node-gyp-bin/node-gyp`, `dist/node-gyp-bin/node-gyp.cmd`, and `dist/node_modules/node-gyp/bin/node-gyp.js`). Without this, `pnpm/action-setup`'s standalone path (used on runners with Node.js < 22.13) failed any install whose lifecycle script invoked `node-gyp rebuild` with `sh: 1: node-gyp: Permission denied` [#11483](https://github.com/pnpm/pnpm/issues/11483).
|
|
26
|
-
|
|
27
|
-
## 11.0.5
|
|
28
|
-
|
|
29
|
-
### Patch Changes
|
|
30
|
-
|
|
31
|
-
- 47b100e: Drop the `darwin-x64` artifact from `@pnpm/exe` and from the GitHub release page. The Node.js SEA mechanism `pnpm pack-app` uses produces a binary that segfaults at startup on Intel Macs because of an upstream Node.js bug ([nodejs/node#62893](https://github.com/nodejs/node/issues/62893), tracked alongside [#59553](https://github.com/nodejs/node/issues/59553); the Node.js team has [opted not to fix it](https://github.com/nodejs/node/pull/60250) on the grounds that x64 macOS is being phased out). Re-signing with `codesign` or `ldid` doesn't help — the corruption is in LIEF's Mach-O surgery, before signing.
|
|
32
|
-
|
|
33
|
-
Intel Mac users should install pnpm via `npm install -g pnpm` (uses the system Node.js, no SEA), or stay on pnpm 10.x. `@pnpm/exe`'s preinstall on Intel Mac now exits with a clear error pointing at these alternatives.
|
|
34
|
-
|
|
35
|
-
Closes [#11423](https://github.com/pnpm/pnpm/issues/11423).
|
|
36
|
-
|
|
37
|
-
## 11.0.3
|
|
38
|
-
|
|
39
|
-
### Patch Changes
|
|
40
|
-
|
|
41
|
-
- a99ffe0: Also pass `verbatimSymlinks: true` to the `fs.cpSync` call in `__utils__/scripts/src/copy-artifacts.ts`, which is the script that actually produces the GitHub release tarballs (`pnpm-{darwin,linux}-{x64,arm64}.tar.gz`). The previous fix in #11399 only covered the `fs.cpSync` in `pnpm/artifacts/exe/scripts/build-artifacts.ts`, which packages the `dist/` shipped inside the npm-published `@pnpm/exe` package. Verified by inspecting the v11.0.2 release tarballs after #11399 landed: the broken `/home/runner/work/pnpm/pnpm/...` symlinks under `dist/node_modules/.bin/` were still present, confirming `copy-artifacts.ts` is the offender for the GitHub release path. Follow-up to #11398.
|
|
42
|
-
|
|
43
|
-
## 11.0.2
|
|
44
|
-
|
|
45
|
-
### Patch Changes
|
|
46
|
-
|
|
47
|
-
- d613c81: Preserve relative symlinks under `dist/node_modules/.bin/` when copying `dist/` for the standalone executable artifact, by passing `verbatimSymlinks: true` to `fs.cpSync`. This stops the release tarballs from baking absolute paths to the build host (e.g. `/home/runner/work/pnpm/pnpm/...`) into symlink targets, which previously made the tarballs unextractable by strict tar implementations that validate symlink targets (e.g. hermit) [#11398](https://github.com/pnpm/pnpm/issues/11398).
|
|
48
|
-
|
|
49
|
-
## 11.0.0
|
|
50
|
-
|
|
51
|
-
### Patch Changes
|
|
52
|
-
|
|
53
|
-
- ef4ef7b: Restored the legacy `@pnpm/{macos,win,linux,linuxstatic}-{x64,arm64}` npm names for the platform-specific optional dependencies of `@pnpm/exe`, reverting the scope-nested `@pnpm/exe.<platform>-<arch>[-musl]` rename from [#11316](https://github.com/pnpm/pnpm/pull/11316) on the published package names only — the workspace directory layout (`pnpm/artifacts/<platform>-<arch>[-musl]/`) and the GitHub release asset filenames stay on the new scheme. The rename broke `pnpm self-update` from v10, which looks up the platform child by its legacy name. `linkExePlatformBinary` now checks for both schemes so a later rename can ship without a v10-compatibility hazard.
|
|
54
|
-
|
|
55
|
-
## 11.0.0
|
|
56
|
-
|
|
57
|
-
### Major Changes
|
|
58
|
-
|
|
59
|
-
- 5a293d2: Renamed the platform-specific optional dependencies of `@pnpm/exe` to the new `@pnpm/exe.<platform>-<arch>[-<libc>]` scheme, using `process.platform` values (`linux`, `darwin`, `win32`) for the OS segment. The umbrella package `@pnpm/exe` itself is unchanged so existing `npm i -g @pnpm/exe` and `pnpm self-update` flows keep working.
|
|
60
|
-
|
|
61
|
-
| before | after |
|
|
62
|
-
| ------------------------- | ---------------------------- |
|
|
63
|
-
| `@pnpm/linux-x64` | `@pnpm/exe.linux-x64` |
|
|
64
|
-
| `@pnpm/linux-arm64` | `@pnpm/exe.linux-arm64` |
|
|
65
|
-
| `@pnpm/linuxstatic-x64` | `@pnpm/exe.linux-x64-musl` |
|
|
66
|
-
| `@pnpm/linuxstatic-arm64` | `@pnpm/exe.linux-arm64-musl` |
|
|
67
|
-
| `@pnpm/macos-x64` | `@pnpm/exe.darwin-x64` |
|
|
68
|
-
| `@pnpm/macos-arm64` | `@pnpm/exe.darwin-arm64` |
|
|
69
|
-
| `@pnpm/win-x64` | `@pnpm/exe.win32-x64` |
|
|
70
|
-
| `@pnpm/win-arm64` | `@pnpm/exe.win32-arm64` |
|
|
71
|
-
|
|
72
|
-
GitHub release asset filenames follow the same scheme — `pnpm-linuxstatic-x64.tar.gz` becomes `pnpm-linux-x64-musl.tar.gz`, `pnpm-macos-*` becomes `pnpm-darwin-*`, `pnpm-win-*` becomes `pnpm-win32-*`. Anyone downloading releases directly needs to use the new filenames; `get.pnpm.io/install.sh` and `install.ps1` will be updated in lockstep to accept both schemes based on the requested version.
|
|
73
|
-
|
|
74
|
-
Resolves [#11314](https://github.com/pnpm/pnpm/issues/11314).
|
|
75
|
-
|
|
76
|
-
## 11.0.0
|
|
77
|
-
|
|
78
|
-
### Major Changes
|
|
79
|
-
|
|
80
|
-
- 491a84f: This package is now pure ESM.
|
|
81
|
-
|
|
82
|
-
## 9.5.0
|
|
83
|
-
|
|
84
|
-
## 7.1.8
|
|
85
|
-
|
|
86
|
-
### Patch Changes
|
|
87
|
-
|
|
88
|
-
- 7fb1ac0e4: Fix pre-compiled pnpm binaries crashing when NODE_MODULES is set.
|
|
89
|
-
|
|
90
|
-
## 6.19.0
|
|
91
|
-
|
|
92
|
-
### Minor Changes
|
|
93
|
-
|
|
94
|
-
- b6d74c545: Allow a system's package manager to override pnpm's default settings
|