admin管理员组文章数量:1414628
I'm working on an electron app that controls gulp tasks via gui. You click on a task and it runs. Pretty simple stuff. On macOS, when I run npm start it runs just fine, but when I package it with electron-packager, I get this error:
Uncaught Exception:
Error: spawn gulp ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _binedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
This is the code:
exports.runTask = (taskName, projPath) => {
const cp = spawn('gulp', [ taskName ], {cwd: projPath});
cp.stdout.setEncoding('utf8');
cp.stdout.on('data', data => {
console.log(data);
mainWindow.webContents.send('task-console-data', data);
});
cp.stderr.setEncoding('utf8');
cp.stderr.on('data', data => {
console.error(data);
displayNotification({text: `[error] ${data}`});
mainWindow.webContents.send('task-console-data', `[error] ${data}`);
});
cp.on('exit', code => {
if (code === 0) {
displayNotification({
title: 'gulp',
subtitle: 'Finished running tasks'
});
} else if ( !code || code === null ) {
return;
} else {
console.error(`Exited with error code ${code}`);
displayNotification({
title: 'gulp',
subtitle: `Exited with error code ${code}`,
sound: 'Basso'
});
}
});
};
I'm working on an electron app that controls gulp tasks via gui. You click on a task and it runs. Pretty simple stuff. On macOS, when I run npm start it runs just fine, but when I package it with electron-packager, I get this error:
Uncaught Exception:
Error: spawn gulp ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _binedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
This is the code:
exports.runTask = (taskName, projPath) => {
const cp = spawn('gulp', [ taskName ], {cwd: projPath});
cp.stdout.setEncoding('utf8');
cp.stdout.on('data', data => {
console.log(data);
mainWindow.webContents.send('task-console-data', data);
});
cp.stderr.setEncoding('utf8');
cp.stderr.on('data', data => {
console.error(data);
displayNotification({text: `[error] ${data}`});
mainWindow.webContents.send('task-console-data', `[error] ${data}`);
});
cp.on('exit', code => {
if (code === 0) {
displayNotification({
title: 'gulp',
subtitle: 'Finished running tasks'
});
} else if ( !code || code === null ) {
return;
} else {
console.error(`Exited with error code ${code}`);
displayNotification({
title: 'gulp',
subtitle: `Exited with error code ${code}`,
sound: 'Basso'
});
}
});
};
Share
Improve this question
asked Jul 17, 2017 at 16:16
Dino MorrisonDino Morrison
1072 silver badges8 bronze badges
2 Answers
Reset to default 4In case anyone else is running into this problem, the answer is to correct the $PATH. There is a package on npm that does this for you.
https://www.npmjs./package/fix-path
You should forward the process.env.PATH
to the spawn options because the child process
environment variables is overriding in options.env
. So the OS don't know exactly where to look your mand gulp
.
So you can do this:
const cp = spawn('gulp', [ taskName ], {
cwd: projPath,
env: {
PATH: process.env.PATH,
},
});
本文标签: javascriptelectronpackager spawn ENOENTStack Overflow
版权声明:本文标题:javascript - electron-packager spawn ENOENT - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1745182839a2646545.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论