Sass slows down quite a bit with this approach about blendid HOT 7 CLOSED

Hi Guys,

I have the same problem.

This is happening on other BrowserSync/Gulp setup, even the one recommended on BrowserSync website.
I also tried to remove autoprefixer & other pipes, but still getting injected all the main scss files.

from blendid.

After further testing i've came to the conclusion that is the access to the config file within the tasks that is slowing everything down.

Removing the references to "source", "build" and plugin configuration from the sass task everything goes back to normal values, including the autoprefixer and sourcemaps tasks.

Update: Actually scratch that, I had an error on the sass file and that was the reason for the fast output. It seems that splitting the gulp file in multiple files always slows things down.

from blendid.

Are you guys returning the streams in your tasks? 5.05 ms seems impossibly fast - like that the task is reporting finished as soon as it runs, instead of as soon as the sass is finished compiling.

from blendid.

Also, I pushed up some changes to the BrowserSync implementation over the weekend. Pull the latest and let me know if your issues persist with the new setup.

from blendid.

Hey Dan,
Thanks for the updates, i'll test them asap.
Regarding the compilation times, I can assure you the difference is quite noticeable. With my "common" gulp file the compilation is pretty much instant.

from blendid.

Hi Dan, im closing this one since it seems there's nothing to do here.
One quick note though. I've noticed on my setup that returning the task does add about 1s to each compilation, that is:

gulp.task('sass-build', function () {
  gulp.src( config.SASS.src )

vs this:

gulp.task('sass-build', function () {
  return gulp.src( config.SASS.src )

from blendid.

@lmartins Cool, thanks. So when you don't return the task, gulp will immediately report that the task has finished, regardless of whether or not the file has finished compiling. You must return a stream, or fire a callback if you want proper task reporting. Otherwise gulp has no way of knowing when it's complete, and immediately moves on to the next thing.

from blendid.