pnpm 12.0.0-rc.1 → 12.0.0-rc.2
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/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# pnpm
|
|
2
2
|
|
|
3
|
+
## 12.0.0-rc.2
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- Globally installed bins can now follow the project you run them in. The new `globalShims` setting is a record of package names to policies that selects which globally installed packages get project-aware shims; it defaults to `{ node: true, deno: true, bun: true }` and merges key-wise, so `globalShims: { bun: false }` switches one default off and `globalShims: { typescript: true }` adds another package. With the default, a project that pins Node.js through `devEngines.runtime` or `engines.runtime` gets the pinned stable release — authenticated against the Node.js release-team signatures — downloaded on first use and run whenever you type `node` inside the project, with no shell hooks. Candidates that are not signature-verified (Deno, Bun, Node.js prereleases, and ordinary package bins you enable) ask "Do you trust this project?" once per candidate and remember the answer machine-locally; the record values name the policy per package: `"auto"` (or its shorthand `true`) defers to artifact authentication, `"always"` switches without ever asking (useful in CI), and `"prompt"` always asks, even for authenticated candidates. Set `globalShims: false` to disable the feature, or `PNPM_SHIM_BYPASS=1` to bypass it for one invocation. On Windows, programs can keep spawning the global `node.exe` directly, without a shell.
|
|
8
|
+
|
|
9
|
+
### Patch Changes
|
|
10
|
+
|
|
11
|
+
- `pnpm dlx` and `pnpm create` no longer fail with "Failed to read patch file" in a project that has `patchedDependencies`. As in pnpm, the package dlx runs is installed unpatched.
|
|
12
|
+
|
|
13
|
+
- Reduced the warm startup overhead of project-aware managed runtime shims.
|
|
14
|
+
|
|
15
|
+
- `ng build` and `nuxt build` now work under the global virtual store: pnpm's built-in compatibility extensions add the `tslib` dependency that `@angular/build` uses without declaring and the `unplugin` dependency that `@nuxt/vite-builder` v4 uses without declaring.
|
|
16
|
+
|
|
17
|
+
- The automatic `packageManager` version switch works again on registries whose tarball URLs point at a different host than the registry itself (load-balanced feed proxies, Artifactory-style mirrors). Package-manager entries are now always recorded with integrity-only resolutions — the download URL is derived from the trusted bootstrap registry instead — and entries persisted in an invalid shape by an earlier pnpm are discarded and re-resolved instead of failing every command [#13619](https://github.com/pnpm/pnpm/issues/13619).
|
|
18
|
+
|
|
19
|
+
- Registries that serve no npm signature metadata (private mirrors and feed proxies commonly strip `dist.signatures`) no longer break the automatic `packageManager` version switch and `pnpm self-update` [#13147](https://github.com/pnpm/pnpm/issues/13147). When the configured registry cannot provide a verifiable signature, pnpm now fetches the signature from `registry.npmjs.org` and verifies it against the same embedded npm keys over the installed integrity — which proves exactly the same thing. If no signature can be obtained from either source (for example, both are unreachable, or the registry publishes only a `shasum`), pnpm proceeds with a warning instead of failing, but only when the packages resolve through a registry configured in the user's own (non-project) configuration; the download stays pinned by the lockfile integrity, and a signature that exists but does not validate still fails the switch.
|
|
20
|
+
|
|
21
|
+
- `pnpm setup` no longer makes Node.js print a `MODULE_TYPELESS_PACKAGE_JSON` warning about `dist/worker.js` on every command. The `package.json` it writes next to a standalone executable now declares `"type": "module"`.
|
|
22
|
+
|
|
3
23
|
## 12.0.0-rc.1
|
|
4
24
|
|
|
5
25
|
### Major Changes
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
{
|
|
2
|
-
"lastValidatedTimestamp":
|
|
2
|
+
"lastValidatedTimestamp": 1786284556806,
|
|
3
3
|
"projects": {
|
|
4
4
|
"/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy": {
|
|
5
5
|
"name": "pacquet",
|
|
6
|
-
"version": "12.0.0-rc.
|
|
6
|
+
"version": "12.0.0-rc.2"
|
|
7
7
|
}
|
|
8
8
|
},
|
|
9
9
|
"pnpmfiles": [],
|
package/package.json
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
"./dist/node_modules/node-gyp/gyp/gyp"
|
|
10
10
|
]
|
|
11
11
|
},
|
|
12
|
-
"version": "12.0.0-rc.
|
|
12
|
+
"version": "12.0.0-rc.2",
|
|
13
13
|
"description": "Fast, disk space efficient package manager",
|
|
14
14
|
"keywords": [
|
|
15
15
|
"pnpm",
|
|
@@ -43,14 +43,14 @@
|
|
|
43
43
|
"dist/"
|
|
44
44
|
],
|
|
45
45
|
"optionalDependencies": {
|
|
46
|
-
"@pnpm/exe.win32-x64": "12.0.0-rc.
|
|
47
|
-
"@pnpm/exe.win32-arm64": "12.0.0-rc.
|
|
48
|
-
"@pnpm/exe.darwin-x64": "12.0.0-rc.
|
|
49
|
-
"@pnpm/exe.darwin-arm64": "12.0.0-rc.
|
|
50
|
-
"@pnpm/exe.linux-x64": "12.0.0-rc.
|
|
51
|
-
"@pnpm/exe.linux-arm64": "12.0.0-rc.
|
|
52
|
-
"@pnpm/exe.linux-x64-musl": "12.0.0-rc.
|
|
53
|
-
"@pnpm/exe.linux-arm64-musl": "12.0.0-rc.
|
|
46
|
+
"@pnpm/exe.win32-x64": "12.0.0-rc.2",
|
|
47
|
+
"@pnpm/exe.win32-arm64": "12.0.0-rc.2",
|
|
48
|
+
"@pnpm/exe.darwin-x64": "12.0.0-rc.2",
|
|
49
|
+
"@pnpm/exe.darwin-arm64": "12.0.0-rc.2",
|
|
50
|
+
"@pnpm/exe.linux-x64": "12.0.0-rc.2",
|
|
51
|
+
"@pnpm/exe.linux-arm64": "12.0.0-rc.2",
|
|
52
|
+
"@pnpm/exe.linux-x64-musl": "12.0.0-rc.2",
|
|
53
|
+
"@pnpm/exe.linux-arm64-musl": "12.0.0-rc.2"
|
|
54
54
|
},
|
|
55
55
|
"scripts": {
|
|
56
56
|
"preinstall": "node install.js",
|