-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Attach stats to data object #428
Comments
Just bumped into this issue again and realized it has not been implemented. |
WraithKenny
added a commit
to WraithKenny/gulp-sass
that referenced
this issue
Jul 21, 2021
The `stats` object that's returned from the sass compiler contains some interesting info, particularly `includedFiles` which can be used to develop smarter watchers. Related to dlmanning#279, fixed dlmanning#428
niksy
pushed a commit
to niksy/gulp-sass
that referenced
this issue
Jan 24, 2022
The `stats` object that's returned from the sass compiler contains some interesting info, particularly `includedFiles` which can be used to develop smarter watchers. Related to dlmanning#279, fixed dlmanning#428
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
First brought up in #279, it would be useful having access to the stats object from node-sass.
My use case: I frequently include scss files from node_modules via
npm link
. If I'm working on those particular modules I have to either manually declare their respective paths to gulp.watch, watch the entire node_modules directory, or trigger my builds manually. I would like to be able to just pull those files from the data object and add them to my watch list downstream.Actually, as I'm writing this I realize I could limit my recursion in my watch task. I would still rather not worry about the performance hit. If I'm missing something else though I'm open to alternatives.
Edit: Sorry, just realizing that #279 became that very issue. Should have just commented there. Apologies.
The text was updated successfully, but these errors were encountered: