Not updating modified timestamp of output when working with @import

gulp-sass does not seem to update the modified date of the generated .css file, instead it uses the same date as the input .scss file.

This leads to problems when using gulp-sass together with rails/sprockets. If I update .scss files that are imported into a global.scss, the created css file will still use the same modified timestamp as the global.scss and sprockets will not load the new file.

In order to fix this, I had to manually update the modified time after gulp-sass:

var touch = require('gulp-touch-cmd');

return gulp.src(config.src)
    .pipe(sass(config.settings))
    .pipe(gulp.dest(config.dest))
    .pipe(touch())  /* fix to update modified time */

Tested with versions 2.0.4 and 4.0.1. Gulp 4.0.0

I’m not sure if this is a problem of gulp-sass or gulp itself.

[WraithKenny]

In the meantime, if anyone needs the output file to have an updated modified/accessed time, you can pipe this before the gulp.dest pipe (requires you add through2)

.pipe( through2.obj( function( file, enc, cb ) {
	var date = new Date();
	file.stat.atime = date;
	file.stat.mtime = date;
	cb( null, file );
}) )
.pipe( gulp.dest( './' ) )

[WraithKenny]

I hope you reconsider.

This plugin is responsible for the compiled css file, and that file that is compiled from it is reporting the wrong modified time. It’s a bug.

https://github.com/dlmanning/gulp-sass/blob/master/index.js#L99 When you are assigning file.contents and file.path, you should just set file.mtime = new Date(); or some such.

EDIT: file.stat.mtime = new Date();