Nodemon shouldn't read the file .nodemonignore every 5 seconds about nodemon

[remy]

Hmm - yeah, nodemon doesn't purposely check every n' seconds - it uses a watch on the file for any changes, then it triggers the read logic - so it's quite possible that FileVault is causing the problem.

Hmm...is there any way to tell FileVault to ignore a directory and give it a test again to confirm (though I'm not sure what I can do to prevent it...).

[morganrallen]

I have noticed this occurs when having two instances on nodemon running in the same directory.

I tested with a basic case.

create two files, noop.js and noop2.js
both contain while(1){};
create a .nodemonignore with anything in it (non-empty)
run nodemon on each file and it will keep displaying the message.

[remy]

@tbassetto do you want to test against the latest version (0.5.3) - @morganrallen sent a pull request that might/should fix this.

[tbassetto]

I can't reproduce the bug, with any version of nodemon. I've changed my computer so I can't tell what fixed it :/

[remy]

Closing for now - happy to reopen if it can be replicated again.