Nodemon leaves old server running when restarting

• nodemon -v: 2.0.2
• node -v: v10.15.2
• Operating system/terminal environment: Windows 10 / VSCode
• Using Docker? What image: No
• Command you ran: nodemon

Appeared suddenly. Can run nodemon, save a file once to restart the server, and then the new server seems to fail to handle any requests. When closing this server and attempting to restart it, says the address is already in use.

[eclectic-coding]

I think it is a problem with system speed and the way the process restart on file changes. It seems to happen too quickly and port is still running IMO.

My work around was to set port: const port = process.env.PORT then use the variable in app.listen(port).

In package.json I changed my script: "start": "PORT=3000 nodemon app.js"

This seems to work for now.

[eclectic-coding]

I can confirm with version 2.0.2 and 2.0.3. I am having the same issues:

events.js:288
      throw er; // Unhandled 'error' event
      ^
Error: listen EADDRINUSE: address already in use :::3000

The project I am working on is at this repo.

For the time being I have included a kill port script in the start script but obviously this is annoying.