-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Major bug was fixed in NPM@10.3.0 concerning apps started with npm start #51923
Comments
This is a duplicate of #48946. npm 10.3.0 is on |
Do you know when the next Node.js 21 release is going live? |
It was planned for last week but I'm not sure why it didn't happen as I was away. |
@richardlau there were some issue with the CI flakiness making impossible to backport. |
node 21.7.0 has been live for around a week, I would consider this solved |
Hi, team, any idea when the updated NPM is coming to LTS, for example 20.11.1, versions? A lot of NodeJs applications that are being launched with "npm start" don't work now causing interruption of DB queries, HTTP requests, etc. |
AFAIK release for 20 is planned for 2024-03-26 @richardlau |
Hi, team, any updates? Shall I expect a delay in the release of NPM@10.5.0 for older node versions? |
Version
20.11.0
Platform
Any
Subsystem
No response
What steps will reproduce the bug?
There was an bug introduced in earlier versions of npmcli/run-script 6.0.2 which prevented signals from reaching child processes of NPM, i.e. applications started with npm start. This is fixed in 10.3.0 of the NPM package. Link to issue npm/run-script@089eefb.
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
Child processes of NPM should receive signals so that they can handle proper shutdown(SIGTERM, SIGINT, etc.)
What do you see instead?
Child processes of NPM are not killed properly, meaning that shutdown processes are no longer executed for nodejs applications started with npm start
Additional information
The Docker team was informed about the problem but responded that Node must update the NPM package available for their versions. nodejs/docker-node#2038
The text was updated successfully, but these errors were encountered: