Server still runs in the background
See original GitHub issueDescription
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:
npm ls react-scripts
(if you haven’t ejected):node -v
: 6.4.0npm -v
: 3.10.3
Then, specify:
- Operating system: Windows 10
- Browser and version: Any
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:30 (11 by maintainers)
Top Results From Across the Web
Server process keeps running in background after stopping ...
Greetings, I'm using Node 6.9.5 on Windows 10. I've been using http-server (installed globally) to test out Webpack generated builds.
Read more >mstsc.exe keeps running in background after closing ...
Hi,. I did quick test with Server 2019 Standard Build 17763.805 running all RDS roles and client PC with Windows 10 Pro 1903...
Read more >Close programs running in the background in Windows
Solution 1: Temporarily disable background programs (short version). Right-click the program's icon in the system tray (next to the clock), and choose Close, ......
Read more >Find out what processes are running in the background on Linux
Explains how to find out what processes are running in the background on Linux using process STATE codes for ps, top, htop commands....
Read more >Keep a function active in background on the server
Make this function independent and it keeps running in the background on server continuously. · Someone told me that if I work though...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue persists when using Git Bash on Windows 10 (multiple different machines). Can we please re-open?
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?