Server still runs in the background

[chaseWillden]

Description

When I run npm start, then I kill the app ctrl+c, the NodeJs server still runs as a task in the background.

Expected behavior

The process should be fully stopped.

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected):
2. node -v: 6.4.0
3. npm -v: 3.10.3

Then, specify:

1. Operating system: Windows 10
2. Browser and version: Any

[thien-do]

Hi @chaseWillden ,

• Is this issue always happen, or just sometimes? (I do meet this issue a few times, but it is quite rarely and I can't reproduce)
• When you kill the app, is it finished its compilation?
• After you kill the app, do you able to access the app via browser? (or just the nodejs server still runs but you can't see the app in browser)
• Can you reproduce this with a new CRA?

[chaseWillden]

@dvkndn

• For me, its every time I press Ctrl+C on command line.
• Yes, it's finished it's compilation and started the developmental server. When I kill it, the server is still running.
• Yes, I can access the app via browser.
• What is CRA?

One important thing to note is I am using the Cygwin terminal.

[thien-do]

oh for the last question, I mean do you able to reproduce the issue with a new create-react-app project? Just after generated?

Hm.. have you ever try to see if it works in any other terminal?

[chaseWillden]

Yes, it happens with new projects. Even when I update the create-react-app on my computer.

I'll check other terminals.

[gaearon]

Can you try debugging why this happens?

[Tev-work]

Happens for me as well in the cygwin terminal (mintty 2.7.1) on windows 7. I created fresh project and only one more folder with component. Ctrl+C stops the script but nothing happens with the node server, I have to kill node through task manager (closing cygwin almost never works).

https://gyazo.com/5038db711e66a2eca13ccec0abef21c1

I don't know how to debug the script btw, any pointer to some tutorial or something would be helpful.

It seems to be running just fine in PowerShell though.

EDIT:
node -v: 6.3.0
npm -v: 3.10.3

[gaearon]

This might be a bug in cross-spawn.
We'd need somebody to create a minimal example with it and verify it's an issue on Cygwin.
Or maybe it's just a Node or Cygwin bug.

[Timer]

Just dropping a note, I've noticed runaway node processes on on macOS too. I'll try to keep an eye out for the cause in the future.

[gaearon]

I also noticed this. We should fix it.

[Timer]

Guessing #1753 solves this?