-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verbose output? #600
Comments
Ok, apparently there is a |
Also can nodemon understand foreman .env files? It seems nodemon picks up file changes but won't restart the underlying exec'd process. |
There's Re: |
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 ignorespackages/*/node_modules
and also make sure it monitors all .js files inpackages/*/
. What's the best way to get more info out of nodemon?The text was updated successfully, but these errors were encountered: