nodemon: Nodemon does not kill process on exit with Git Bash on Windows 10

I’m on Windows 10. When I start a server with nodemon app.js two Node.js instance appear in the Task Manager. If I use Git Bash command line when exit nodemon by pressing ctrl+c one of the Node.js process still running in the background, I’ve to kill that process manually to exit the server. If I use PoweShell or Cmder/cmd it works fine, both process are killed on exit.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 11
Comments: 25 (4 by maintainers)

Most upvoted comments

Updating git bash to 2.16 fixed this.

+13

tresdev on Mar 7, 2018

I solved this by creating a nodemon.json file in my root directory and adding and added the following: “events”:{ “restart”:“fuser -k 8000/tcp && nodemon server” }

+12

aodr3w on Nov 18, 2019

I’m also experiencing this issue running:

Git for Windows 2.15.1(2)
Node v8.9.1
npm v5.5.1

As a workaround I keep a cmd.exe shell open and just run: taskkill /F /IM node.exe to kill Node processes. I don’t get any EADDRINUSE errors this way.

greyscaled on Dec 3, 2017

I resolved the issue by using Windows PowerShell instead of git bash, it is installed with Windows so you don’t need to install anything extra. If you start your nodemon application with PowerShell and press Ctrl + C then you will get the following message Terminate batch job (Y/N)? . Entering ‘Y’ here and then pressing enter will do the job.

To open PowerShell in the same way you open git bash by right-clicking inside folder, replace default CMD with PowerShell by following the steps mentioned here. After that you can just go to folder go to folder you want to open PowerShell to and press Shift + Right Click, this will show an extra option in menu saying Open PowerShell window here.

zeus2198 on Nov 1, 2017

@remy nodemon@1.12.6 worked in my env. Thanks for the fix!

tanyaYourchuck on Dec 13, 2017

Can someone try with the latest release: nodemon@1.12.6 (on node > 4)? It uses fork instead of spawn so it might solve this problem.

remy on Dec 13, 2017

@vapurrmaid yes, I’m using git bash, but using a gulp task to launch the process rather than npm script. In my env with nodemon v1.12.5, ctrl + c did not hang, it returned to prompt but left the node process running (thus still using the port). This was fixed with nodemon v1.12.6.

I tried to run the gulp task in an npm script. Then I observed same as you describe, ctrl+c just hung.

tanyaYourchuck on Dec 14, 2017