Error: EPERM, rename '...something...'

[dy]

I use watchify as a npm task in windows, and periodically it stops watching and logs

{ [Error: EPERM, rename 'c:\Users\dmitry\Dropbox\Projects\mod\dist\mod.js']
  errno: 50,
  code: 'EPERM',
  path: 'c:\\Users\\dmitry\\Dropbox\\Projects\\mod\\dist\\mod.js' }

Restarting fixes it for a while utill the next EPERM error.

[highwaycoder]

+1

[plus-]

👍

[divmgl]

Yeah what is this about? I still can't figure it out. Maybe write access has been blocked in these situations?

[terebentina]

To me it happens when I save a file, watchify kicks in then I quickly save again, before watchify finishes rebuilding the first time.
It is very annoying as it means I have to keep watching the watchify task to make sure it still rebuilds every time.

[highwaycoder]

I also get it under those circumstances, which occur more frequently for me
when I'm using WebStorm or have an editor set up to behave like WebStorm
(saving every time I make a change).

On Tue, Oct 14, 2014 at 12:12 PM, Dan Caragea notifications@github.com
wrote:

To me it happens when I save a file, watchify kicks in then I quickly save
again, before watchify finishes rebuilding the first time.
It is very annoying as it means I have to keep watching the watchify task
to make sure it still rebuilds every time.

Reply to this email directly or view it on GitHub
#83 (comment).

[dy]

Yes, I have sublime's always save option enabled, so that's probably the case.

[j201]

+1

[terebentina]

Upon further investigation, using a gulp task with watchify is both faster and doesn't seem to suffer from this problem. For me only watchify from the command line had this problem.

[davepile]

Today I upgraded to watchify 2.1.1
I had previously been getting this EPERM error quite frequently and it did seem that it happened after quickly saving several files, or the same file, in quick succession.

After the upgrade I again got this error and it was definitely not the result of quickly saving files. Below is the error I received and the previous save was some 20 - 30 seconds earlier and resulted in correct output (or at least a notification in the terminal that the output was written correctly, i didnt test the actual bundle.js)
{ [Error: EPERM, rename 'C:\work\projects\cordova\propman\www\js.bundle.js']
errno: 50,
code: 'EPERM',
path: 'C:\work\projects\cordova\propman\www\js.bundle.js' }

Hope this helps

[j201]

I can reproduce it with watchify 2.1.1 by doing the following:

• Create a JS file test.js with a syntax error
• watchify test.js -o test-out.js (Prints a ParseError)
• Remove the syntax error
• Save test.js (no errors yet)
• Save test.js again

This produces the following:

{ [Error: EPERM, rename 'C:\Users\alex\Documents\temp\test-out.js']
  errno: 50,
  code: 'EPERM',
  path: 'C:\\Users\\alex\\Documents\\temp\\test-out.js' }

Now that I can reproduce it, I'll take a look at possible fixes when I get a chance.

[jednano]

@j201 your repro steps give me the same error.

[jednano]

FWIW, I have a Node script I use to remedy the problem in my scenario. Perhaps it might be useful to fix the issue as well as for people to use before it gets fixed:

var browserify = require('browserify');
var fs = require('fs');
var mkdirp = require('mkdirp');
var watchify = require('watchify');

var args = process.argv.slice(2);
var env = args[0];
var shouldWatch = args[1] === '--watch';

var options = (shouldWatch) ? watchify.args : {};

var b = browserify(options);

if (shouldWatch) {
    b = watchify(b);
    b.on('update', rebundle);
}

b.add('./lib/index.js');

var outdir = './dist/';
mkdirp.sync(outdir);
rebundle();

function rebundle() {
    var outpath = outdir + '/index-bundle.js';
    b.bundle().pipe(fs.createWriteStream(outpath));
}

I hope it's helpful to someone.

[manuelcabral]

For some reason this seems to fix it on my system: digisfera@f3f61b4

While there isn't a more permanent fix, you can try this version with npm install digisfera/watchify