.nodemonignore doesn't work on nodemon versions 0.6.19 and 0.6.20 #107

tomgco opened this Issue Jun 7, 2012 · 5 comments

5 participants


It seems that on a Mac, nodemon@0.6.19 and nodemon@0.6.20 -- not sure if 0.6.20 has been pushed to GH -- does not acknowledge the rules in .nodemonignore tested on node 0.6.18 and 0.6.19.

Rolling back to nodemon@0.6.18 has fixed this behaviour.

@vadimi vadimi added a commit to vadimi/nodemon that referenced this issue Jun 7, 2012
@vadimi vadimi Fix for issue #107
Also fixes issue with node restart on Windows after file change.

This fix should resolve the problem with .nodemonignore. I tested it on Windows 7 only.


Just tested this on Mac OS X 10.7.4 and Node.js 0.6.19 and seems to work for me.


.nodemonignore still works, sorta, just not like it should.

This bug was caused by my commit. (Sorry, folks.) I moved the check for ignored files from changeFunction to startMonitor in order to prevent fs.watch from watching tons of ignored files unnecessarily.

I hadn't realized that fs.watch is looking at directories too, and that means a change within a directory will trigger a reload even if the file itself was ignored. To use the example from the documentation, if you ignore /vendor/* then you're going to miss changes in /vendor. If, on the other hand, you ignore /vendor*, the old behavior should be restored.

The ideal solution is probably to watch directories only, and to test for ignored files both in changeFunction and startMonitor.

I haven't reviewed vadimi@08e5aa1 at all, but I could go ahead and implement my proposed fix if there's anything wrong with vadimi's fix.


applied the patch and it works fine :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment