-
-
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
Regression: Still watching too many files #1364
Comments
@remy This is still an issue...
|
I saw and reported the same behaviour before - see #1320 (specifically my comment). Including a file in the watch list causes the entire project project directory to be watched for me. |
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. |
@remy The stale bot compelled me to mention you :-) |
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. |
Wow, stalebot is persistant. This is related to #1320 When watching a file, nodemon switches to watching the dir, and then recursively watches the sub dirs. |
Confirmed. |
nodemon -v
:1.15.1
and1.17.1
and1.17.5
node -v
:v9.6.1
andv10.3.0
Expected behaviour
Should watch only the files set in
--watch
orwatch
config innodemon.json
Actual behaviour
Watches many files beyond the defined directories and files
Steps to reproduce
1.14.12
https://github.com/alexilyaev/express-github-login/tree/nodemon-v1.14.12
1.15.1
https://github.com/alexilyaev/express-github-login/tree/nodemon-v1.15.1
1.17.1
https://github.com/alexilyaev/express-github-login/tree/nodemon-v1.17.1
Note
If I remove the single file matches it works ok.
If applicable, please append the
--dump
flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.The text was updated successfully, but these errors were encountered: