blocks|key|4495450|text|它基本上是说，它无法产生您的进程，不是由于权限，而是因为您的脚本中的错误。Source|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4495451|执行NODE_ENV=production+node+app.js没有任何问题吗？|style|CODE|4495452|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/npm/npm/blob/448efd0eaa6f97af0889bf47efc543a1ea2f8d7e/lib/utils/lifecycle.js#L208^0|11|6|0|0|2|V|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

It's basically saying it fails to spawn your process not due to permission but to an error in your script. <a href="https://github.com/npm/npm/blob/448efd0eaa6f97af0889bf47efc543a1ea2f8d7e/lib/utils/lifecycle.js#L208">Source</a>

You don't have any problem executing <code>NODE_ENV=production node app.js</code> ?

blocks|key|4494514|text|在运行Webpack构建时，我收到了类似的错误，因为node不能理解旧版本中的async+await关键字。我加了webpack+babel-plugin-transform-async-to-generator，解决了。这用承诺取代了它们。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4494515|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/babel-plugin-transform-async-to-generator^0|13|5|19|5|1T|15|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

When running Webpack build I was getting similar error because node doesn't understand <code>async</code> <code>await</code> keywords on older versions. I added webpack <a href="https://www.npmjs.com/package/babel-plugin-transform-async-to-generator" rel="noreferrer">babel-plugin-transform-async-to-generator</a> and it was solved. This replaces them with promises.

blocks|key|4495521|text|如果你像我一样来到这里，在尝试React+Getting+Started+guide时收到类似的错误，你可能想知道这个问题可能是由于没有安装Watchman造成的。请在此处下载，或与带有brew+install+watchman的Homebrew一起安装，然后重试：https://facebook.github.io/watchman/docs/install.html|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4495522|PS:你可能想先做一个brew+update。|4495523|entityMap|0|LINK|mutability|MUTABLE|url|https://facebook.github.io/react-native/docs/getting-started.html|1|https://facebook.github.io/watchman/docs/install.html^0|2L|L|F|R|0|3P|1H|1|0|B|B|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]|$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

If you came here like I did, after receiving a similar error when trying the <a href="https://facebook.github.io/react-native/docs/getting-started.html" rel="noreferrer">React Getting Started guide</a>, you might like to know that the problem could have been caused by not having installed Watchman. Download it here, or install it with Homebrew with <code>brew install watchman</code> and try again: <a href="https://facebook.github.io/watchman/docs/install.html" rel="noreferrer">https://facebook.github.io/watchman/docs/install.html</a>
PS: You might want to do a <code>brew update</code> first.

blocks|key|4494602|text|在安装或更新新软件包后，我也遇到了同样的错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494603|...
npm+ERR!+code+ELIFECYCLE
npm+ERR!+errno+1
...|code-block|syntax|javascript|4494604|它帮助我再次或多次运行安装命令。在那之后，错误消失了。|4494605|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same error after I installed new packages or updated them:

<pre><code>...
npm ERR! code ELIFECYCLE
npm ERR! errno 1
...
</code></pre>

It helped me to run installation command once again or a couple of times.
After that, the error disappeared.

blocks|key|4495556|text|在我的例子中，这是因为RAM内存太低，照片压缩库无法处理更大的照片。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4495557|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, it was because of low RAM memory, when a photo compression library was unable to process bigger photos.

blocks|key|4494648|text|当我运行两个具有相同设置的项目时，我遇到了这个问题，并且我已经有一个项目在运行。这意味着另一个项目不能使用该端口号。一旦我停止了另一个项目的运行，我就没有问题了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494649|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this issue when I was running two projects that had the same set up and I already had one running. This meant that the other project couldn't use that port number. As soon as I stopped the other project running I had no issues.

blocks|key|4494691|text|在我的例子中，这是Linux的权限问题，而不是写成：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494692|npm+run+start|code-block|syntax|javascript|4494693|我试过了：|4494694|sudo+npm+run+start|4494695|然后输入你的sudo用户密码，你就可以开始了！|4494696|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case it was permission problem with Linux, instead of writing:

<pre><code>npm run start
</code></pre>

I tried: 

<pre><code>sudo npm run start
</code></pre>

Then put your sudo user password and you're good to go!

blocks|key|4495665|text|在我的例子中，当我从另一个目录复制项目时，我生成了一个类似的错误。一些隐藏的文件丢失了，比如critical+.babelrc。所以啊哈。确保复制所有文件！:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4495666|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I generated a similar error when I copied the project over from another directory. some hidden files, like the critical .babelrc, were missing. SO ahhh... make sure you copy all the files!
:)

blocks|key|4494745|text|当您从git中提取代码，但尚未安装节点模块"npm+install“时，也会出现此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494746|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This issue can also occur when you pull code from git and not yet installed node modules "npm install".

blocks|key|4494767|text|对我来说，这是一个三元声明：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494768|它特别抱怨这一行，关于分号：|4494769|let+num_coin+=+val.num_coin+?+val.num_coin+%7C%7C+2;|code-block|syntax|javascript|4494770|我将其更改为：|4494771|let+num_coin+=+val.num_coin+%7C%7C+2;|4494772|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For me it was a ternary statement:

It was complaining about this line in particular, about the semicolon:

<pre><code>let num_coin = val.num_coin ? val.num_coin || 2;
</code></pre>

I changed it to:

<pre><code>let num_coin = val.num_coin || 2;
</code></pre>

blocks|key|4494796|text|Windows解决方案与Linux+sudo答案相同。以管理员身份运行npm+start+(或其他任何命令)。我在我的项目中添加了一个新模块。在一些机器上工作，但在其他更受限制的机器上工作，不是很多。花了一段时间才弄明白，但新模块需要访问“某些东西”，而这些东西在没有管理员权限的情况下是不可用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494797|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The Windows solution is the same as the Linux sudo answer. Run the npm start (or whatever) as Administrator. I had added a new module to my project. Worked on some machines but on others that were more locked down, not so much. Took a while to figure it out but the new module needed access to "something" that wasn't available without administrator permissions.

blocks|key|4494829|text|同样，我看到这个错误是由于RAM太少造成的。我启动了虚拟机上的RAM，错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494830|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Likewise, I saw this error as a result of too little RAM. I cranked up the RAM on the VM and the error disappeared.

blocks|key|4495859|text|我在这里找到了解决方案--+https://javahowtos.com/guides/124-docker/418-npm-exit-status-137-when-building-a-docker-image.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4495860|它说-这种特定的npm错误状态的原因通常意味着Docker内存不足。因此，当这种情况发生时，Linux内核就会终止该进程。|4495861|entityMap|0|LINK|mutability|MUTABLE|url|https://javahowtos.com/guides/124-docker/418-npm-exit-status-137-when-building-a-docker-image.html^0|E|2Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I found the solution here - <a href="https://javahowtos.com/guides/124-docker/418-npm-exit-status-137-when-building-a-docker-image.html" rel="nofollow noreferrer">https://javahowtos.com/guides/124-docker/418-npm-exit-status-137-when-building-a-docker-image.html</a>
It says - The cause of this specific npm error status usually means that Docker is going out of memory. So, when this happens, the Linux kernel just kills the process.

blocks|key|4494908|text|如果您使用的是ubuntu，请检查您的nodejs版本。请将版本更新为最新版本，并清除缓存，然后重新安装模块(npm安装)和内部版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4494909|或者其他|4494910|请升级您的RAM大小，然后重试。它肯定会工作的。|4494911|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

if you are running on ubuntu, please check your nodejs version. please update the version to the latest and clear the cache and reinstall the modules (npm install) and build.
or otherwise
please upgrade your RAM size and try again. it'll work sure.

What does ELIFECYCLE mean?

Here's my app code: <a href="https://gist.github.com/samholmes/388ca4552c5936b52c5d">https://gist.github.com/samholmes/388ca4552c5936b52c5d</a>

When I run the 'blast-emails' command, it will run for a while until shortly crashing with the error:

<pre><code>npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "/root/.nvm/versions/io.js/v1.6.1/bin/iojs" "/root/.nvm/versions/io.js/v1.6.1/bin/npm" "run" "live"
npm ERR! node v1.6.1
npm ERR! npm v2.7.1
npm ERR! code ELIFECYCLE
npm ERR! emailer@0.0.0 live: `NODE_ENV=production node app.js`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the emailer@0.0.0 live script 'NODE_ENV=production node app.js'.
npm ERR! This is most likely a problem with the emailer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=production node app.js
npm ERR! You can get their info via:
npm ERR! npm owner ls emailer
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /apps/emailer/npm-debug.log
</code></pre>

The <code>npm-debug.log</code> file is also included in the gist.

I'm looking for one of two answers: What does ELIFECYCLE mean? (or) Why am I getting the error in my application code?

What does the ELIFECYCLE Node.js error mean?

ELIFECYCLE是什么意思？下面是我的应用程序代码：当我运行'blast-emails‘命令时，它会运行一段时间，直到很快崩溃并出现以下错误：npm ERR! Linux 3.2.0-4-amd64npm ERR! argv "/root/.nvm/versions/io.js/v1.6.1/bin/iojs" "...

问ELIFECYCLE Node.js错误是什么意思？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ELIFECYCLE Node.js错误是什么意思？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ELIFECYCLE Node.js错误是什么意思？
EN