Error: EPERM: operation not permitted, chmod

const gulp = require('gulp');
const sass = require('gulp-sass');
const csso = require('gulp-csso');
const autoprefixer = require('gulp-autoprefixer');
const uglify = require('gulp-uglify');
const addsrc = require('gulp-add-src');
const concat = require('gulp-concat');
const imageResize = require('gulp-image-resize');

const targetDir = 'dist';

gulp.task('default', ['sass', 'js', 'thumbnails']);

gulp.task('sass', () => {
    return gulp.src('src/scss/**/*.scss')
        .pipe(sass().on('error', sass.logError))
        .pipe(addsrc('src/css/**/*.css'))
        .pipe(autoprefixer())
        .pipe(csso())
        .pipe(concat('style.css'))
        .pipe(gulp.dest(targetDir))
});

// (...)

What’s wrong that gulp sass doesn’t have permissions to write to dist/style.css when current user is in group that is owner of this file?

[ahmedelbougha]

Actually, it’s a Linux issue not a gulp issue. The problem is that only the owner of a file or root users can change the permissions of of a file, but group users are not allowed to do so. The solution that I did to fix this problem is to change the owner of the file in following way: chown myuser:http . -R Of course with keeping permissions as 775 or 755. This way Apache user (as group user) is still allowed to run/read the files and my user is allowed to run glup command with tasks including chmod.

[lustosa]

@jorismak exactly. gulp shouldn’t be attempting to chmod anything, it’s not its purpose. As a very dirty workaround, I’ve been using the code below for the past few years. Just put it somewhere in the gulpfile, and it should bypass the actual chmod call:

const fs = require(‘fs’)

if (1) { fs.chmod = (a, b, cb) => cb(0) }