nodemon -v: 1.12.1 and 1.17.5 (I have tried nodemon@latest)node -v: 8.4.0npm -v: 5.0.3When I save my sever.js file, it should console.log('test') again and the port it is listening at.

Not sure how to reproduce it.
It is the exact same issue as: #813
I know this isn't a lot of information, but I don't know much and I'm hoping by creating this it will highlight if I'm not the only one with this issue. If you need anything else from me, please let me know.
First question: does it suddenly drop into a restart loop?
If so, can you include the output but run nodemon using the --verbose flag?
Hello, @remy I am somewhat active on GitHub, and have been facing the issue for quite a while now.
Let me know how I can help.
Yes, sometimes it suddenly drops into a restart loop, and when I used --verbose before, it restarted on every file being opened by Node require(...) function, I don't even open them in my text editor or anything.
Can't reproduce the bug now, using nodemon with --verbose, will post the results once it happens again.
EDIT:
This is how it looks on the first start:
> set NODE_ENV=DEV&& set DB=LOCAL&& nodemon --inspect server.js --verbose
[nodemon] 1.17.5
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 20948 to restart
[nodemon] watching: *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node --inspect server.js`
[nodemon] spawning
[nodemon] child pid: 18824
Debugger listening on ws://127.0.0.1:9229/2010891c-ec54-4f31-a2cc-b027724ff74e
For help, see: https://nodejs.org/en/docs/inspector
[nodemon] watching 1007 files
(node:21756) ExperimentalWarning: The fs.promises API is experimental
Autotash is running DEV on port 3000 !
And this is how it looks when it keeps restarting (trimmed 700 lines in the middle)
[nodemon] files triggering change check: modules\users\team\controllers\users.team.controller.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Modules\users\team\controllers\users.team.controller.js
[nodemon] files triggering change check: modules\users\team\controllers\authentication\authentication.team.login.controller.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Modules\users\team\controllers\authentication\authentication.team.login.controller.js
[nodemon] files triggering change check: modules\users\team\controllers\profile\profile.list.customer.team.controller.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Modules\users\team\controllers\profile\profile.list.customer.team.controller.js
... trimmed 700 lines here, basically the same thing
[nodemon] files triggering change check: modules\vendors\team\controllers\managers\vendors.managers.unassign.team.controller.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Modules\vendors\team\controllers\managers\vendors.managers.unassign.team.controller.js
[nodemon] starting `node --inspect server.js`
[nodemon] spawning
[nodemon] child pid: 16904
Debugger listening on ws://127.0.0.1:9229/7aeb20b1-2e44-4b78-b400-1179cd9c396f
For help, see: https://nodejs.org/en/docs/inspector
(node:12296) ExperimentalWarning: The fs.promises API is experimental
Autotash is running DEV on port 3000 !
as https://github.com/remy/nodemon/issues/1354#issuecomment-392681579
try to run fsutil behavior set disablelastaccess 1 from an elevated shell.
did it fix it?
Gave it a try, as an initial result, the bug was fixed.
I'll post here if the issue happens again.
EDIT :
3 days after, the bug hasn't still come back. https://github.com/remy/nodemon/issues/1354#issuecomment-392681579 probably solves it!
Hi all, it's been a long time but I found a solution to my problem at last.
If I run nodemon locally, it works fine, it only does this when I run it globally.
I've tried uninstalling and reinstalling globally, but no luck. No idea why this is the case, but we can close now.
@TFKED how did you install nodemon locally? I used npm install nodemon without the g, but when I tried to run it, my terminal said that it doesn't recognize nodemon as a command.
@awesomebanana123 it won't. You have to run it like this if running locally: ./node_modules/.bin/nodemon --watch server.js
Most helpful comment
as https://github.com/remy/nodemon/issues/1354#issuecomment-392681579
try to run
fsutil behavior set disablelastaccess 1from an elevated shell.did it fix it?