Import change not triggering parent file re-compile.

[ShaneHowell]

I'm having an issue with the parent file not re compiling when an import is changed.
For example, I have a base file called global.scss which imports a partial _header.scss.

But when the _header.scss is changed, it doesn't recompile global.scss.
The watch task is seeing the file being changed but its parent doesn't recompile.

[gulp] _header.scss was changed

Watch function:

// Watch SCSS
    gulp.src(input_paths.styles, { read: false })
        .pipe(plumber())                                // Keeps pipes working after error event
        .pipe(watch())                                  // Watches for file changes
        .pipe(scss( scss_options ))                     // SCSS compiler
        .pipe( gulp.dest( output_paths.styles ) )       // Output destination
        .pipe(livereload(server))                       // Reload the page
        .pipe( notify( notify_options ) );              // Notify what file was changed

scss_options variable:

// Sass
    var scss_options = {
        outputStyle: 'compressed', // variables - https://github.com/andrew/node-sass
        errLogToConsole: false,
        onError: function(err) {
            notify().write(err);                    // Growl it.
            console.log(gutil.colors.red(err));      // Log the occurred error.
            process.stdout.write('\x07');          // Beep boop the terminal.
        }
    };

Not 100% sure this is a gulp-sass issue though.

[apaleslimghost]

If you use the built-in gulp.watch, when you change any of the files they are all recompiled. libsass is fast enough that this isn't really a problem.

gulp.watch('app/scss/*.scss', ['sass-watch']);
gulp.task('sass-watch', function() {
  return gulp.src('app/scss/*.scss')
    .pipe(sass(sassOptions))
    .pipe(gulp.dest('app/css'))
    .pipe(livereload());
});

[ShaneHowell]

@quarterto IMO, no watch set up should have to recompile every file when only one file has changed. It may be fast but it would still shave off many seconds by only compiling changed files.

I've also tested it both ways. While libsass is fast, it's exponentially faster when only compiling changed files, especially on larger projects.

[apaleslimghost]

Then use gulp-newer or gulp-changed.

EDIT actually, this has the same problem. sorry!

[dlmanning]

As @quarterto suggests, this is outside the domain of gulp-sass. gulp plugins are not supposed to be one-stop-shops for the entire build process. gulp-sass's only job is to allow the inclusion of node-sass in a build chain.

[ShaneHowell]

Apologies, I did in fact post this issue to the wrong plugin.

[apaleslimghost]

@ShaneHowell just found gulp-sass-graph

[nucklearproject]

This plugin solve this issue
https://www.npmjs.com/package/gulp-dependents