Nodemon restart twice when change is made

Question

I am using nodemon in order to restart the app when change is made. It works good however it restart two times and thus sometimes it is a bit busy to read data returned from server (like console.log) since its reloaded twice.

I am talking about something like this:

[nodemon] starting `node app.js`
Connected to db and listening on port 8080
[nodemon] restarting due to changes...
[nodemon] starting `node app.js`
Connected to db and listening on port 8080

I am working with Atom IDE.

If this question is missing information, please comment and I will update in case its not fully informative.

Thank you for support.

[follow this](https://github.com/remy/nodemon/issues/763) – yogesh agrawal Jan 29 '18 at 16:45 — yogesh agrawal, Jan 29 '18 at 16:45

score 2 · Answer 1 · answered Oct 01 '21 at 14:29

2

The solution that worked for me was adding the -L flag. nodemon -L fileName.js

answered Oct 01 '21 at 14:29

Krish Garg

73
2
6

Katie Mary · Answer 2 · 2018-01-29T17:30:34.707

1

Possible Solution:

I would start by looking into the set of files/directories nodemon is watching. It may be currently configured to watch two different server files which is why it would restart twice for a single file change. If this is true for you, the solution is as simple as changing your config in order to manage only one extension.

edited Jan 29 '18 at 17:30

answered Jan 29 '18 at 16:27

Katie Mary

82
3

Its is not the solution you can refer this [link](https://github.com/remy/nodemon/issues/763) to see what exact problem is – yogesh agrawal Jan 29 '18 at 16:46
try to get solution and edit your answer @katie Mary – yogesh agrawal Jan 29 '18 at 16:54

Nodemon restart twice when change is made

2 Answers2

Linked