Nodemon: Verbose output?

Created on 30 Jul 2015 · 3Comments · Source: remy/nodemon

nodemon doesn't seem to be working as expected. I start it from a Makefile that looks like this (I use foreman to load my .env file):

watch:
    ./node_modules/.bin/nodemon --exec foreman -- run ./scripts/test.sh

And it runs tests for all directories in packages/ (each have their own node_modules/ directory). So I would like to make sure that nodemon ignores packages/*/node_modules and also make sure it monitors all .js files in packages/*/. What's the best way to get more info out of nodemon?

Source

olalonde

Most helpful comment

There's --verbose which gives you more output. For debugging you can also set the env value of DEBUG=nodemon,nodemon:* and it will list exactly what it's watching.

Re: .env files, no, that's specific to foreman, but I thought that foreman would push all those env values into the shell it runs nodemon in, and nodemon will pass all those to the node instance.

remy on 19 Sep 2015

🎉5

All 3 comments

Ok, apparently there is a --verbose flag. Reduced the amount of files watched with --ignore "packages/*/node_modules". It is still a bit slow (seems to be eating my CPU). Is there any way to get a better performance on OS X?

olalonde on 30 Jul 2015

Also can nodemon understand foreman .env files? It seems nodemon picks up file changes but won't restart the underlying exec'd process.

olalonde on 30 Jul 2015

There's --verbose which gives you more output. For debugging you can also set the env value of DEBUG=nodemon,nodemon:* and it will list exactly what it's watching.

Re: .env files, no, that's specific to foreman, but I thought that foreman would push all those env values into the shell it runs nodemon in, and nodemon will pass all those to the node instance.

remy on 19 Sep 2015

🎉5

Was this page helpful?

0 / 5 - 0 ratings