-
-
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
Display (w/ or w/o path) which file has changed and triggered restart #551
Comments
See docs around events. It's supported.
|
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. |
I read https://github.com/remy/nodemon/blob/master/doc/events.md but still can't where did the document record that. But it is easy to do that by |
same here.... I think it would be super helpful if @remy could make this feature more explicitly documented. An use case here is https://cmty.app/nuxt/nuxt.js/issues/c10464 |
I've got a
...and there's sometimes so much output that the one crucial line about the one crucial change that wasn't filtered gets overwritten by the runner's output (ultra's spinners). It'd be great if there was an option to only output changes that passed the filters. |
@remy can you share a link to the docs for this? Or should the issue be reopened? |
Would it be possible to have nodemon display which file has been changed to trigger a restart? I'm sure this would be most helpful especially when the output is piped to and consumed by another process.
I'm not sure if this feature exists already.
If it is, someone please kindly tell me how to get it working with the latest nodemon npm package.
If it isn't already implemented, is there any interest for this feature?
My request spawns from watching
grunt serve
output that shows file changes like below:Nodemon could provide something like this:
It'd be great to have something like this from nodemon as well.
The text was updated successfully, but these errors were encountered: