Repository navigation
Try: Strict, isolated installs on npm 12 with manifest repairs - #82849
Draft
manzoorwanijk wants to merge 3 commits into
Draft
manzoorwanijk wants to merge 3 commits into
manzoorwanijk wants to merge 3 commits into
Conversation
🤖 PR meta 🤖📦 Bundle sizeSize Change: +4.2 kB (+0.05%) Total Size: 8.98 MB 📦 View Changed
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
🏁 Flaky testsSome tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information. Regression: updating a specific option will only change its value and will not corrupt others in
|
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
3 times, most recently
from
September 17, 2026 11:48
fd59fde to
fbf2588
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
3 times, most recently
from
September 18, 2026 08:29
48d39ed to
015225a
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
September 25, 2026 06:45
015225a to
f202999
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
2 times, most recently
from
October 1, 2026 11:34
60017a1 to
b445dc0
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
October 2, 2026 03:45
b445dc0 to
896b859
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
October 2, 2026 06:46
896b859 to
ea8f5a5
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
October 2, 2026 08:55
ea8f5a5 to
8847b40
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
2 times, most recently
from
October 5, 2026 04:41
115fa78 to
2c5f760
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
5 times, most recently
from
October 7, 2026 04:56
9f60ea0 to
9dd3fd9
Compare
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
October 14, 2026 13:16
9dd3fd9 to
ca29778
Compare
Bump engines.npm and devEngines.packageManager to npm v12, now that the supply chain policy the major requires has landed in #82689. Drop the npmrc settings v12 makes redundant with it: git and remote specs are refused by default, and the lockfile already records its own version. Generate the icons library from the root postinstall. v12 holds workspace lifecycle scripts to allowScripts under install-strategy=linked and skips an unlisted one with no error (npm/cli#9982), so the approval was fragile. Root lifecycle scripts are outside the policy, so building from postinstall drops the entry entirely. Closes #82328.
Under install-strategy=linked a package only resolves what it declares, so packages whose types or peer ranges are wrong now fail the install. Repair their manifests at the root, each linked to its upstream issue. Fold the version overrides in as well, so each repair sits next to the reason for it: the js-yaml and pacote releases lerna pins below their advisories, the uuid release sockjs no longer publishes for, and the @y/y alias @y/websocket-server needs to share one Yjs implementation. The eslint overrides go with them, since the peer repairs above already cover those plugins, and the jsdom pin matched what test/unit asks for.
Under install-strategy=linked the root copy hid every workspace and dependency that uses React types without declaring them. - Routes and the welcome widget declare @types/react; compose and ui declare @types/react-dom for their tests. - @wordpress/route peers on react-dom, which @tanstack/react-router requires. - .npm-extension.mjs adds an optional @types/react peer to third-party packages whose declarations import React types without declaring them.
manzoorwanijk
force-pushed
the
try/npm-12-isolated-strict-install
branch
from
October 20, 2026 12:21
ca29778 to
36d13f8
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
See #82328.
Throwaway PR stacking npm 12 and manifest repairs on the isolated, strict install already in trunk, so CI exercises them together. The npm 12 slice lands separately through #82732, and the rest follows as its own PR.
Why?
To find what breaks before splitting it up.
How?
.npm-extension.mjs, each next to its upstream issue or advisory.@types/reactand@types/react-domleave the root; every workspace that uses them declares them.Testing Instructions
npm install --global npm@12node_modules, thennpm ci.npm run typecheck && npm run build && npm run test:unitTesting Instructions for Keyboard
None.
Use of AI Tools
Built with Claude Code; reviewed by the author.