spawn dist/electron.exe ENOENT

win10 + 64 node.js 5.1.1 + 32

  "dependencies": {
    "ffi": "^2.0.0"
  },
  "devDependencies": {
    "electron-prebuilt": "^0.36.0",
    "electron-rebuild": "^1.0.2"
  }

• exec

.\node_modules\.bin\electron-rebuild.cmd

• error info

spawn dist/electron.exe ENOENT
Error: spawn dist/electron.exe ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:452:9)
    at process._tickCallback (node.js:366:17)

node_modules\electron-prebuilt\dist\electron.exe is exist

[rspieker]

I had a similar problem on OSX (same error, different executable of course). OSX 10.10.5 / OSX 10.11.1 Node.js 5.0.0 / 5.1.0

Worked around it by changing node_modules/electron-rebuild/lib/spawn.js

Around line 25, there is this code:

  return new _Promise(function (resolve, reject) {
    var error = null;
    //console.log("Calling spawn! " + JSON.stringify(options));
    var proc = _child_process2['default'].spawn(options.cmd, options.args, options.opts);

Changed it to provide the cwd (current working directory) to the spawn command

  return new _Promise(function (resolve, reject) {
    var error = null;
    if (!('cwd' in options.opts)) {
        options.opts.cwd = process.cwd() + '/node_modules/electron-prebuilt';
    }
    //console.log("Calling spawn! " + JSON.stringify(options));
    var proc = _child_process2['default'].spawn(options.cmd, options.args, options.opts);

I’m sure this isn’t the way to go (as the paths on various OS’s will differ), hence I haven’t made a pull request.

[felicienfrancois]

@tomprogers

But electron-prebuilt throws a fatal error at startup unless I use the original path

Why don’t you use the original path ?