-
-
Notifications
You must be signed in to change notification settings - Fork 33k
Major bug was fixed in [email protected] concerning apps started with npm start #51923
Copy link
Copy link
Closed
Closed
Copy link
Labels
npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.
Description
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
Metadata
Metadata
Assignees
Labels
npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.