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?

[gaearon]

Maybe.

[ericjasonthomas]

I have the same issue mac OS node v7.6.0 npm 4.1.2

[Geczy]

Same issue as @ericjasonthomas

[gaearon]

Hopefully this is fixed by #2246.
Let me know if you see this again with react-scripts >= 1.0.1.

[gaearon]

react-scripts@1.0.1 should be out with a fix.
Can you please verify it helps?

[scifutures]

This is concerning behavior -- I can't seem to stop it and it's taken over port 8888. Restarted twice now and it doesn't stop even after restart. I don't see any processes running node and there aren't any startup scripts that stand out that would be causing it.

---

Edit: It appears that its some form of progressive webapp enhancement that keeps the app in offline storage. I stopped the node process and then went into Inspector -> Applications -> Clear Storage, cleared everything, now the app goes away. It's not loading the offline app now, which is likely the source of the issue.

[gaearon]

Yes, as noted both in migration notes for 1.0 and in User Guide, the default template now includes a service worker that ensures the app can be cached for offline use (and, importantly, near-instant recurrent visits). The User Guide also includes instructions to opt out (you can remove the service work registration call from src/index.js). Does this help?

[a19c97]

@gaearon I tried removing registerServiceWorker() from index.js, but the process still persists after ctrl-c or ctrl-z. (I'm running npm 3.10.10 on Cygwin.) Any other ideas? It's really annoying to have to kill the process in task manager every time.

[mfish0005]

I can confirm this as happening for me on Windows 10. I've been working on several apps bootstrapped with CRA. Some ejected, some not. Some with registerServiceWorker, some not. I've become accustomed to pressing CTRL+SHIFT+ESC to open task manager and manually kill anything with the word node in it.

It might be worth noting that this only happens if I'm using Git Bash. If I run the process in my IDE's shell(VS Code) pressing CTRL+C kills the process as expected.

[armyofda12mnkeys]

This also occurs for me. Using Cygwin on Windows 10. Just killed via Task Manager like above user.

[joelwross]

This issue persists when using Git Bash on Windows 10 (multiple different machines). Can we please re-open?

[sheep-sheep]

As @joelwross said, I also observed same issue on Windows 10 with Git Bash, when Ctrl+C terminate the job, the port is still occupied and website is accessible. (I'm using the demo page).

CMD doesn't have the problem.

[divyanshu-rawat]

Observed same issue 👍

[Maxeh]

I'm also having this problem.

[nathanhannig]

Having issue after updating to recent CRA

[HynekS]

Same issue, Windows 7, Git Bash.
Edit: Switching from Git Bash to Cmder or windows shell seems to fix this problem, which suggests that the underlying issue is related to Git Bash, rather than create-react-app.

[cormacrelf]

Possibly unrelated, but react-scripts build never terminates when it has a "cannot find file" error. It just prints out what's wrong, and hangs there, not consuming CPU, just stalled. (And it's impossible to cancel Netlify builds, so I'm just stuck. Great.)

./src/App.tsx
Cannot find file './results-csl.json' in './src'.

[charlesritchea]

@gaearon I'm using react-scripts 2.1.1 and this issue is still present on Windows 10 using vscode terminal.

[benparkinson]

@gaearon still seeing this in cygwin, Windows 10, react-scripts 2.1.1.

[sunnyYanan]

still having this problem