Skip to content

Possible NodeJS 22.22.2 regression when installing latest NPM #62425

Closed
Closed
Possible NodeJS 22.22.2 regression when installing latest NPM#62425
Sachchaa/react-timegrid
#28
 (+1)
Labels
npmIssues and PRs related to the npm client dependency or the npm registry.v22.xIssues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.

Description

@altbdoor
altbdoor
opened on Mar 25, 2026

Version

v22.22.2

Platform

Darwin M-FC6WJYY430 25.3.0 Darwin Kernel Version 25.3.0: Wed Jan 28 20:56:35 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T6030 arm64

Subsystem

No response

What steps will reproduce the bug?

# use the latest node 22.x
nvm install 22.22.2

# activate the node version
nvm use 22.22.2

# install latest npm
npm install -g npm@latest

How often does it reproduce? Is there a required condition?

Always happens.

What is the expected behavior? Why is that the expected behavior?

NPM should install successfully.

What do you see instead?

npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'
npm error Require stack:
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/index.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/index.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/node_modules/libnpmfund/lib/index.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/utils/reify-output.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/utils/reify-finish.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/commands/install.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/npm.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/cli/entry.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/lib/cli.js
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/bin/npm-cli.js

Additional information

Created a minimal reproducible matrix of Node and NPM versions in https://github.com/altbdoor/node-22-npm-regress/actions/runs/23525843427/job/68478996014 .

For brevity:

Node NPM Success?
22.22.1 ^11.12.0 OK
22.22.1 ^11.11.0 OK
22.22.1 latest OK
22.22.2 ^11.12.0 NOK
22.22.2 ^11.11.0 NOK
22.22.2 latest NOK

Edit: seems to only happen from a new Node 22.22.2 environment, doing npm install -g npm@latest. Installing the versions in increment appears to be OK.

$ npm i -g npm@^10

changed 13 packages in 1s

$ npm i -g npm@~11.10

removed 48 packages, and changed 92 packages in 1s

$ npm i -g npm@~11.11

removed 1 package, and changed 26 packages in 902ms

$ npm i -g npm@~11.12

removed 7 packages, and changed 22 packages in 905ms

$ npm i -g npm@latest

changed 10 packages in 1s

Activity

  1. MikeMcC399 commented on Mar 25, 2026

    @MikeMcC399
    MikeMcC399
    on Mar 25, 2026
    Contributor

    Also reproducible on Ubuntu 24.04.4 LTS and only on Node.js 22.22.2. Other security releases (20.20.2, 24.14.1 & 25.8.2) are not affected.

    Possibly this should also be reported to https://github.com/npm/cli/issues

  2. tiagosiebler commented on Mar 25, 2026

    @tiagosiebler
    tiagosiebler
    on Mar 25, 2026

    Easily reproducible in ubuntu latest running in a container (#62430) and on Mac Sequoia after nvm switch to v22.22.2

  3. rethab
    added a commit that references this issue on Mar 25, 2026

    fix(sysupgrade): disable nvm/npm upgrade due to node v22.22.2 regression

    30018b3

  4. ctataryn-qh commented on Mar 25, 2026

    @ctataryn-qh
    ctataryn-qh
    on Mar 25, 2026

    Same problem for me when running npm i -g npm

  5. MikeMcC399 commented on Mar 25, 2026

    @MikeMcC399
    MikeMcC399
    on Mar 25, 2026
    Contributor

    Also reported in npm/cli#9151

  6. MickLesk
    added 2 commits that reference this issue on Mar 26, 2026

    fix(tools.func): pin npm to 11.11.0 to work around Node.js 22.22.2 re…

    aee9f8f

    fix(tools.func): pin npm to 11.11.0 to work around Node.js 22.22.2 re…

    b9a39db
  7. owlstronaut
    added a commit that references this issue on Mar 26, 2026

    fix: eagerly require promise-retry to survive self-upgrade

    49ab7ba

  8. MikeMcC399 commented on Mar 26, 2026

    @MikeMcC399
    MikeMcC399
    on Mar 26, 2026 · Hidden as outdated
  9. owlstronaut
    added a commit that references this issue on Mar 27, 2026

    fix: eagerly require promise-retry to survive self-upgrade

    8aa9c82

  10. owlstronaut commented on Mar 27, 2026

    @owlstronaut
    owlstronaut
    on Mar 27, 2026

    #62463. Tested locally myself but would love to hear from others once it's released

  11. Renegade334
    linked a pull request that will close this issue[v22.x] deps: upgrade npm to 10.9.8 #62463on Mar 27, 2026

  12. altbdoor commented on Mar 27, 2026

    @altbdoor
    altbdoor
    on Mar 27, 2026
    Author

    @owlstronaut I manually updated NPM in Node 22.22.2 to the new version, and it works.

    $ nvm use 22
Using Node v22.22.2

$ npm --version
10.9.7

$ npm i -g npm@10.9.8
changed 17 packages in 7s

$ npm i -g npm@latest
removed 55 packages, and changed 89 packages in 17s
  13. unflxw
    added a commit that references this issue on Mar 31, 2026

    Pin npm to fix build for Laravel

    44744c0

  14. timtrense-leadec commented on Mar 31, 2026

    @timtrense-leadec
    timtrense-leadec
    on Mar 31, 2026

    Reproducible as a oneliner via docker run --rm -it --entrypoint bash node:22-bookworm -c "npm i -g npm@latest"

    npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'
npm error Require stack:
npm error - /usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js
npm error - /usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/index.js
npm error - /usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/index.js
npm error - /usr/local/lib/node_modules/npm/node_modules/libnpmfund/lib/index.js
npm error - /usr/local/lib/node_modules/npm/lib/utils/reify-output.js
npm error - /usr/local/lib/node_modules/npm/lib/utils/reify-finish.js
npm error - /usr/local/lib/node_modules/npm/lib/commands/install.js
npm error - /usr/local/lib/node_modules/npm/lib/npm.js
npm error - /usr/local/lib/node_modules/npm/lib/cli/entry.js
npm error - /usr/local/lib/node_modules/npm/lib/cli.js
npm error - /usr/local/lib/node_modules/npm/bin/npm-cli.js

    Our CI pipeline logs confirm that the issue was not present at 2026-03-24 09:36 UTC.

    I can confirm that first installing a non-latest version works, like @altbdoor said:
    docker run --rm -it --entrypoint bash node:22-bookworm -c "npm i -g npm@10.9.8 && npm i -g npm@latest" --> Successful

  15. 104 remaining items

  16. willwashburn
    added 2 commits that reference this issue on Jul 9, 2026

    ci: pin Node to 22.22.3 to avoid 22.22.2 npm toolcache regression

    4fd2177

    ci: bump pinned Node to 22.22.2 to fix npm@latest EBADENGINE (#246)

    8e44333
  17. clavery
    added a commit that references this issue on Jul 9, 2026

    ci(publish): move publish job to Node 24 to fix npm publish failure

    db7361f
  18. brandonlehmann
    added 2 commits that reference this issue on Jul 21, 2026

    Unpin Node in publish job

    23407bf

    Unpin the publish job Node version and refresh the lockfile

    998c20a
  19. github-actions
    added a commit that references this issue on Jul 21, 2026

    Build: (998c20a) Unpin the publish job Node version and refresh the l…

    25fe519
  20. SurvicatePawelGodlewski
    added 2 commits that reference this issue on Jul 22, 2026

    fix(ci): unpin Node in publish workflow

    5d19cea

    Release/8.3.1 (#145)

    8932461
  21. quitting7oh
    added a commit that references this issue on Aug 22, 2026

    fix(build): move Node pin to 24.15.0; 22.22.2 ships a broken npm

    3ca14a8
  22. bedrich-schindler
    added 3 commits that reference this issue on Aug 24, 2026

    Pin `npm` to version to prevent npm issues from breaking the build

    f2d9888

    Pin `npm` to version to prevent npm issues from breaking the build

    ba57f69

    Pin `npm` to version to prevent npm issues from breaking the build

    69865b4
  23. dinhanhthi
    added a commit that references this issue on Aug 25, 2026

    fix(ci): pin npm to 11.11.0 to avoid self-upgrade regression

    786e0a0
  24. MickLesk
    added 2 commits that reference this issue on Sep 1, 2026

    Say what the npm 10.9.7 block is actually for

    04bcc97

    Silence npm's update notice so the real error stays visible (#16)

    11666dc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    npmIssues and PRs related to the npm client dependency or the npm registry.v22.xIssues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions