Closed Atulin closed 3 years ago
We don't manage gulp-sass.
Well it's not an issue with gulp-sass
. Let me give you a link to the relevant issue again, you might've missed it or forgotten to click it: https://github.com/Mister-Hope/gulp-sass/issues/11
Mind you, the issue exists no matter which implementation of gulp-sass
I use.
@Atulin if the problem doesn't exist when not using the gulp-sass plugin, then it's a problem with that plugin or your setup... Neither of which we are responsible for.
So it's a problem with two independently-developed gulp-sass
plugins, where each of them is but a thin wrapper around SASS? I guess it's, time to raise an issue on the SASS repo as well
Before you open this issue, please complete the following tasks:
What were you expecting to happen?
I expect using globs like
/static/css/**/*.sass
for a watcher would result in progressively faster compilation times with each triggerWhat actually happened?
They become progressively longer
Please give us a sample of your gulpfile
results in
while
results in
with the following tasks
and the following packages
Please provide the following information:
node -v
): 14.10.1npm -v
): 7.5.4gulp -v
): 4.0.2 (local) 2.3.0 (CLI)Additional information