Nodemon won't kill previous process after upgrade from node v10 to v16

[talhaanees]

• Versions: Node 16.0.0, win32 Windows 10 x64, OS 10.0.19043, Electron 11.4.10
• nodemon -v: 2.0.13

Expected behaviour

Nodemon would kill the previous electron process and restart after changes occur

Actual behaviour

Nodemon starts a new process (sometimes multiple processes) when the changes occur. Every save does this

Steps to reproduce

Everything was working fine with node v10. This started happening after upgrading to node v16. I have tried passing --signal in the command, which doesn't work.

the script that I run is is:
"electron-watch": "nodemon --watch ./electron.cjs --exec "npm run electron-start""

Any ideas why this started happening after the upgrade and how I can fix it?

[remy]

No idea, but try node 14 to see if you can narrow it down?

[immortalmind2016]

@remy i think this issue related to this PR : #1938

[remy]

Can people following this thread test with npm i nodemon@debug and confirm if this works or not - this is the latest change with @immortalmind2016's changes.

[Sigmanor]

Can people following this thread test with npm i nodemon@debug and confirm if this works or not - this is the latest change with @immortalmind2016's changes.

seems with npm i nodemon@debug it's working correctly

[remy]

This is live in the latest release, so we can close this then.

[talhaanees]

Confirmed this issue is resolved with nodemon v: 2.0.14!

[JoeyFlaum]

@remy Still running into issues. Nothing is working. Please help.

[nodemon] 2.0.15
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node server.js`
Server is running on port 3000
rs
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...

[remy]

@JoeyFlaum can you file a new issue with details on how to replicate with pared down code.