-
Notifications
You must be signed in to change notification settings - Fork 860
Show notice of sass gulp task running #1144
Comments
@Aetles looks like some of the gulpfile code I wrote in the previous version didn't get ported over in the Foundation 6.4 update for FP. Gulp was updated to v4 and the watch method is different now. I'll get this sorted out soon. |
May I add to this that it would be nice to get noticed if errors appear during the process? I am not proficient enough to add this myself, but I have been using a gulp file that had this function that took care of that:
Comes in very handy if you are watching your browser and nothing is happening ;-) |
I was using an older FoundationPress project (back in the grunt days!) and it had this nice progress and report for every SASS change, like this:
I've yet to figure out how to make the latest workflow present this kind of information (or any at all) when re-compiling sass. |
Relevant issue olefredrik#1144. Updates the watch task with event listeners on change and unlink events for the php and sass watch tasks.
#1210 solves this issue, thank you! |
This is not a bug, just a question.
On older FoundationPress projects whenever the watch gulp task found changes in .scss files there was a notice on the command line. But on my latest project the sass task runs fine but does not produce any notice, unless there is an error. Is there anything I can change in
gulpfile.babel.js
to make it always show output again?How can this bug be reproduced?
npm start
What did you expect to happen?
A notice on the command line telling me that the sass task ran, like:
What happened instead?
Nothing. (The sass task do run, it's just not telling me about it.)
Please List the Following:
node_modules/foundation-sites/package.json
) : 6.4.1The text was updated successfully, but these errors were encountered: