Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] npm error Exit handler never called! #7669

Closed
2 tasks done
Vikybad opened this issue Jul 19, 2024 · 11 comments
Closed
2 tasks done

[BUG] npm error Exit handler never called! #7669

Vikybad opened this issue Jul 19, 2024 · 11 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps

Comments

@Vikybad
Copy link

Vikybad commented Jul 19, 2024

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

No response

Expected Behavior

No response

Steps To Reproduce

  1. In this environment...
  2. With this config...
  3. Run '...'
  4. See error...

Environment

  • npm:
  • Node.js:
  • OS Name:
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here
@Vikybad Vikybad added Bug thing that needs fixing Needs Triage needs review for next steps labels Jul 19, 2024
@Sebastian-Webster
Copy link

I'm having this issue as well. I've noticed it only happens only on Node.js 22.5.0. I had a GitHub Actions workflow with the following matrix:
os: [ ubuntu-20.04, ubuntu-22.04, windows-2019, windows-2022, macOS-12, macOS-13, macOS-14 ]
node-version: [18.x, 19.x, 20.x, 21.x, 22.4.0, 22.4.1, 22.5.0 ]
All workflows worked except for the ones running node 22.5.0

@DoLoop216
Copy link

I have same issue and it started today. I have workflow runs which build my docker images and I run them multiple times a day.
Last time it worked was yesterday (18.07.2024)

image

Jobs are running on:

  Ubuntu
  22.04.4
  LTS
  Image: ubuntu-22.04
  Version: 20240714.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240714.1/images/ubuntu/Ubuntu2204-Readme.md

@marvingbh
Copy link

same issue

@matteobe
Copy link

Same issue
Also yesterday working, no changes and today not working

@alex-weber
Copy link

same issue on Heroku. Build fails using 22.5.0
22.4.1 works fine

@Sebastian-Webster
Copy link

Sebastian-Webster commented Jul 19, 2024

An example GitHub Actions workflow with this issue can be found here: https://github.com/Sebastian-Webster/npm-reproducible-example/actions/runs/10007074269. It's only failing on Node 22.5.0. Both npm ci and npm install

@actualben
Copy link

actualben commented Jul 19, 2024

This npm install error is happening on the node:22@sha256:b44cbfafe84144217b7502cde5d21958500781fb9b13eed74a47486db2277cd5 docker tag. It's notable that npm exits 0 after it fails. I have a filtered error log excerpt.

  • npm -v: 10.8.2
  • node -v: v22.5.0
  • OS Name: Debian 12
  • System Model Name: N/A - happening on both ARM64 and AMD64
  • npm config ls:
node bin location = /usr/local/bin/node
node version = v22.5.0
npm local prefix = /build
npm version = 10.8.2
cwd = /build
HOME = /root

@gopivr
Copy link

gopivr commented Jul 19, 2024

Any work around for this issue.. Still facing this issue

@alex-weber
Copy link

Any work around for this issue.. Still facing this issue

use node 22.4

@milaninfy
Copy link
Contributor

Closing Seems similer if not duplicate of #7657.
Try node 22.4.1 with npm 10.8.2.

@milaninfy
Copy link
Contributor

Fixed in Node.js v22.5.1 nodejs/node#53902 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps
Projects
None yet
Development

No branches or pull requests

9 participants