[BUG] Exit handler never called during clean-install, with Node.js v22.5.0

[divergentdave]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

(While there are similar issues already open, the wiki page for "exit handler never called" errors recommends opening a new issue, so I am doing so)

I am running into errors when using Node.js v22.5.0 and npm v10.8.2 to install dependencies. In GitHub Actions, I'm seeing an "Exit handler never called!" error. I tried installing the same versions locally, and instead npm never exits -- the packages get installed, but I just see a spinner in the terminal forever. I did not have any issues in CI prior to the release of Node.js v22.5.0. When I use Node.js v20.12.2 and npm v10.8.2 locally, installation completes successfully. Thus, I think some change in Node.js v22.5.0 must be related.

Here's a log file from the error happening in GitHub Actions: 2024-07-17T17_07_43_972Z-debug-0.log. This came from the following run: https://github.com/divviup/divviup-api/actions/runs/9978466717/job/27575428716?pr=1178

Expected Behavior

npm ci should succeed and exit cleanly.

Steps To Reproduce

1. Install Node.js v22.5.0.
2. Install npm v10.8.2.
3. git clone https://github.com/divviup/divviup-api.git
4. cd divviup-api/app
5. git checkout 3edafaefe90795387db3e35a161f3110c3ac3dea
6. npm ci

Environment

• npm: v10.8.2
• Node.js: v22.5.0
• OS Name: Ubuntu
• System Model Name: Unknown, Azure instance
• npm config:

; node bin location = /opt/hostedtoolcache/node/22.5.0/x64/bin/node
; node version = v22.5.0
; npm local prefix = /home/runner/work/divviup-api/divviup-api/app
; npm version = 10.8.2
; cwd = /home/runner/work/divviup-api/divviup-api/app
; HOME = /home/runner
; Run `npm config ls -l` to show all defaults.

[coreynolan]

Experiencing the same issue with Node v22.5.0. As a temporary fix, I reverted my workflow to my previously used version.

        uses: actions/setup-node@v4
        with:
          node-version: 22.4.x

Interested to hear when a fix is made.

[ABenavidesCTR]

We are having the same issue on our GitHub actions, and we confirmed that yesterday the actions were working while using v22.4.1, but started to fail today when the v22.5.0 version was used. Setting the version to the previous one as @coreynolan suggested worked.

[ljharb]

I'm getting this as well.

[Charlie-Brownie]

Also getting this in Azure Pipelines.

[rileyseaburg]

Can confirm I receive this issue in Jenkins

[GooGam]

Can confirm the same issue with Google Cloud Build