gulp.dest uses chmod on files

When I pipe my compiled css into gulp.dest(folder) it will fail with an error:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: EPERM, chmod 'css/screen.css'

This is because screen.css already exits and only gets overriden - however the user running gulp isn’t the owner of the file.

This is a bug since according to the documentation chmod gets applied to new folders only: options.mode - Octal permission string specifying mode for any folders that need to be created for output folder.

Code:

var gulp = require('gulp');
var sass = require('gulp-sass');
gulp.task('default', function() {
    gulp.src(sassUri + '**/*.{scss,sass}')
        .pipe(sass())
        .pipe(gulp.dest('css'));
});

PS: If this isn’t a bug but a feature, how can I turn this off (or handle it properly)?

[hashworks]

Yeah, I understand how chmod works on GNU/Linux. But on my systems gulp can and will by run by many different users (which are in the same group, though). IMO gulp has absolutely no need to run chmod on this file, since he only needs to write to it.

If I’m unable to turn of this feature I’m absolute ok with catching and ignoring it - my only intention is that the watcher doesn’t fail because of this. Could you show me an example how to catch this error?

[yocontra]

@hashworks There was a bug with the chmod stuff in 3.x - feel free to use the 4.0 stuff it’s stable, just waiting on a few more issues to land before we publish