Skip to content

[BUG] npm >= 9.6.7 does not pass signals to the running script #6547

@zdm

Description

@zdm

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

I have docker sontainer with nodejs application.
Application started using npm run prod command.
It starts script main.js.
This script waiting for SIGTERM and exits.

With npm <= 9.6.6 - when I send TERM signal, to the container it works as expected.
With npm >= 9.6.7 - main script just not receive signal.

Tested with all nom versions from 9.6.5 - 9.7.1.
Bug was introduced in v9.6.7.

Expected Behavior

Please, see above.

Steps To Reproduce

Please, see above.

Environment

  • npm:
  • Node.js:
  • OS Name: ubuntu
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bugthing that needs fixingNeeds Triageneeds review for next stepsRelease 8.xwork is associated with a specific npm 8 release

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions