Skip to content
This repository has been archived by the owner on Jan 6, 2021. It is now read-only.

CTRL+C does not kill the child process #139

Closed
slavik57 opened this issue Aug 31, 2017 · 1 comment
Closed

CTRL+C does not kill the child process #139

slavik57 opened this issue Aug 31, 2017 · 1 comment

Comments

@slavik57
Copy link

I have a start script to run my express server:
"start": "cross-env MY_ENV=1 node ./dist/server.js"
When it runs my express app starts listening on some port
When I hit CTRL+C it exists but the node precess of express still alive

I use windows 10 but I think it's an issue of spawn, you spawn a process and dont send he signal to it when you recieve it...

@slavik57
Copy link
Author

I think it's more of npm issue npm/npm#4603

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant