-
Notifications
You must be signed in to change notification settings - Fork 143
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
Log which file changed with Gulp #151
Comments
Why would you expect only files that changed to trigger? |
Because of the logging of the changes. Grunt-wiredep has this functionality. |
(please forgive my delay!) |
In my experience yes. (please forgive my delay!) |
Oh man, we are full of delays. Sorry for this one, too :( In non-stream mode, here's how we're detecting if we need to write new content : wiredep/lib/inject-dependencies.js Line 127 in 571d469
Maybe we should do something similar for the stream mode: wiredep/lib/inject-dependencies.js Line 144 in 571d469
|
PR welcome! |
Can I just say: Thank you for linking to specific commits (tag would have been okay, too) and not master? |
:) So important to remember to do that, but I most often forget. For anyone who doesn't know already, select a line as normal, then press |
Whoa, I didn't know that trick! I always just navigated to the commit/tag. Very nice trick! |
that sounds like a bug then since if a file wasn't updated then it shouldn't trigger that event |
Is it possible to do that? I got task like below, but it logs all files in stream instead of only files, which changed.
The text was updated successfully, but these errors were encountered: