Repository navigation
npm i -g npm@latest -> Cannot find module 'promise-retry' #62430
Description
Version
v22.22.2
Platform
MacOS Sequoia 15.6.1, but also on "ubuntu-latest" in a container.
Subsystem
No response
What steps will reproduce the bug?
npm i -g npm@latest
How often does it reproduce? Is there a required condition?
Always, since moving to v22.22.2 (from v22.22.0)
What is the expected behavior? Why is that the expected behavior?
Should be able to install latest
What do you see instead?
npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'
npm error Require stack:
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/index.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/index.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/node_modules/libnpmfund/lib/index.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/utils/reify-output.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/utils/reify-finish.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/commands/install.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/npm.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/cli/entry.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/lib/cli.js
npm error - /Users/ts/.nvm/versions/node/v22.22.2/lib/node_modules/npm/bin/npm-cli.js
npm error A complete log of this run can be found in: /Users/ts/.npm/_logs/2026-03-25T10_37_59_708Z-debug-0.log
Additional information
No response
Activity
tiagosiebler commentedon Mar 25, 2026
Oh, duplicate of #62425, my bad
fix: pin npm to 11.11.0 in changesets workflow to work around Node 22…
Use Node 24 on release runner, drop npm self-upgrade step
fix(ci): bump runner node from 22 to 24 to avoid broken bundled npm
fix(ci): use Node 24 for npm OIDC trusted publishing
Use Node 24 in release workflow to fix npm install (#16045)
ci(publish): pack in build, publish tarball in publish
chore: simplify publish workflow & switch node version
fix(release-cli): bump to Node 24 for trusted-publishing-capable npm
fix(ci): publish SDK on Node 24 (Node 22.22.2 npm upgrade broken) (#267)
fix(setup): make npm self-upgrade best-effort in setup script (#219)
Tighten cloud env scripts: drop npm self-upgrade, add setup.sh drift …