当我得到以下错误:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:1000:11)
    at Process.ChildProcess._handle.onexit (child_process.js:791:34)

我该采取什么程序来修理呢?

作者注:这个错误的许多问题鼓励我发布这个问题,以供将来参考。

相关问题:

using spawn function with NODE_ENV=production node.js child_process.spawn ENOENT error - only under supervisord spawn ENOENT node.js error https://stackoverflow.com/questions/27603713/nodejs-spawn-enoent-error-on-travis-calling-global-npm-package Node JS - child_process spawn('npm install') in Grunt task results in ENOENT error Running "foreman" task Fatal error: spawn ENOENT unhandled error event in node js Error: spawn ENOENT at errnoException (child_process.js:975:11) Node.js SpookyJS: error executing hello.js https://stackoverflow.com/questions/26572214/run-grunt-on-a-directory-nodewebkit Run exe file with Child Process NodeJS Node: child_process.spawn not working on Java even though it's in the path (ENOENT) spawn ENOENT error with NodeJS (PYTHON related) image resizing is not working in node.js (partial.js) (non-installed dependency) npm install error ENOENT (build dependency problem) Cannot install node.js - oracle module on Windows 7 (build dependency problem) Error installing gulp using nodejs on windows (strange case)


当前回答

对我来说,我在package.json中做了以下更改。

  "version": "0.0.0",
  "scripts": {
    "dev": "vite --open",    // delete this line
    "dev": "vite",           // with this one
   .....
  }

其他回答

Windows解决方案:用节点交叉生成替换生成。例如,在你的app.js的开头:

(function() {
    var childProcess = require("child_process");
    childProcess.spawn = require('cross-spawn');
})(); 

将C:\Windows\System32\添加到path环境变量。

步骤

进入我的电脑和属性 点击高级设置 然后是环境变量 选择Path,然后单击edit 如果不存在,则粘贴以下文件:C:\Windows\System32\ 关闭命令提示符 运行您想要运行的命令

如何研究刷出调用引起的错误:

使用NODE_DEBUG=child_process, Credits to @karl-richter。简单,快速,2019年10月 使用包装器来装饰child_process。刷,积分到@jiaji-zhou。简单,快速,2015年1月 漫长的过程,归功于@laconbass。复杂,时间成本,2014年12月

已知的常见原因

Environment issues The command executable does not exist within the system (dependency not being installed). see prominc's answer The command executable does not exist within a directory of those specified by PATH environment variable. The executable binary was compiled with uncompatible libraries. see danilo-ramirez answer Windows-only bugs/quirks '.cmd' extension / shell: true. see li-zheng answer Administrator permisions. see steve's answer Wrong spawn('command', ['--argument', 'list'], { cwd, env, ...opts }) usage Specified working directory (opts.cwd) does not exist · see leeroy-brun's answer Argument list within command String spawn('command --wrong --argument list') Env vars within command string spawn('ENV_VAR=WRONG command') Argument list Array specified as String spawn('cmd', '--argument list') Unset PATH env variable spawn('cmd', [], { env: { variable } } => spawn('cmd', [], { env: { ...process.env, variable } }


ENOENT有两种可能的起源: 您正在编写的代码 您依赖的代码 当源代码是你依赖的代码时,通常的原因是环境问题(或windows怪癖)


对于Windows上的ENOENT, https://github.com/nodejs/node-v0.x-archive/issues/2318#issuecomment-249355505修复它。

如更换产卵(npm, [' v '], {stdio:“继承”}):

对于所有node.js版本: 产卵(/ ^赢/ test (process.platform) ?npm。Cmd ': 'npm', ['-v'], {stdio: 'inherit'}) 对于node.js 5。X及以后: 产卵(npm, [' v '], {stdio:“继承”,外壳:真})

简单地添加shell: true选项解决了我的问题:

不正确的:

const { spawn } = require('child_process');
const child = spawn('dir');

正确的:

const { spawn } = require('child_process');
const child = spawn('dir', [], {shell: true});