Skip to content

Update npm-shrinkwrap.md - #1

Open
saifktk5383 wants to merge 117 commits into
latestfrom
patch-1
Open

Update npm-shrinkwrap.md#1
saifktk5383 wants to merge 117 commits into
latestfrom
patch-1

Conversation

@saifktk5383

Copy link
Copy Markdown
Owner

No description provided.

wraithgar and others added 30 commits March 4, 2026 08:49
This contains the changes from

- a2154cd (npm#8996)
- 880ecb7 (npm#9013)
- 26fa40e (npm#9041)
- 983742b (npm#9055)
- 10d5302 (npm#9051)
- a29aeee (npm#9028)
- 16fbe13 (npm#9030)
- 8614b2a (npm#9031)

Since Node 22 doesn't have npm 11 yet, it would be better to have this
change backported to v10


Also, we wish to use `install-strategy=linked` in the [Gutenberg
monorepo](WordPress/gutenberg#75814), which
powers the WordPress Block Editor. We are still on v10. So, these fixes
will help.
Cherry pick of:
- 5fd40b6 (npm#9076)
- e2c2443 (npm#9081)

Additional changes:

- Ported `shouldOmit` method to v10's `Node` class (exists on `latest`
but was missing on v10) with full test coverage
…fixes (npm#9120)

This is a cherry-pick of 

- 8e0a731 - npm#9108 
- 51365b1 - npm#9107
- 21ea382 - npm#9110 

and cf34e6f (the changes needed for
21ea382 in v10 branch)
These were deep in the tree, with dev dependencies being hoisted.
We try to hoist production deps in favor of dev dependencies
When npm 10.x upgrades itself to npm 11.12+, the new npm no longer
bundles promise-retry. The lazy require in _linkBins fires after
the reify step has already deleted promise-retry from disk, causing
MODULE_NOT_FOUND. Moving the require to the top of the file ensures
it is loaded at startup while the module still exists on disk.

Fixes: npm#9151
Ref: nodejs/node#62425
Backport of npm#9317 to `release/v10`.

Co-authored-by: Michael Smith <owlstronaut@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants