ELIFECYCLE npm错误 [英] ELIFECYCLE npm error

问题描述

这是我的控制台中的错误

This is the error in my console

npm ERR! code ELIFECYCLE
npm ERR! errno 3221225477
npm ERR! sedona@0.1.0 start: `npm run build && gulp serve`
npm ERR! Exit status 3221225477
npm ERR!
npm ERR! Failed at the sedona@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging
output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\User\AppData\Roaming\npm-cache\_logs\2017-07-21T19_40_30_516Z
-debug.log

这是来自AppData/Roaming等路径的"debug.log"文件

This is the "debug.log" file from AppData/Roaming etc. path

0 info it worked if it ends with ok
1 verbose cli [ 'D:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@5.3.0
3 info using node@v8.2.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle sedona@0.1.0~prestart: sedona@0.1.0
6 info lifecycle sedona@0.1.0~start: sedona@0.1.0
7 verbose lifecycle sedona@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle sedona@0.1.0~start: PATH: D:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\User\Desktop\user.github.io\node_modules\.bin;C:\Users\User\Desktop\cmder\bin;C:\Users\User\Desktop\cmder\vendor\git-for-windows\cmd;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5\ConEmu;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\Skype\Phone\;D:\Program Files\nodejs\;C:\Users\User\AppData\Roaming\npm;C:\Users\User\Desktop\cmder\vendor\git-for-windows\usr\bin;C:\Users\User\Desktop\cmder\vendor\git-for-windows\usr\share\vim\vim74;C:\Users\User\Desktop\cmder\
9 verbose lifecycle sedona@0.1.0~start: CWD: C:\Users\User\Desktop\user.github.io
10 silly lifecycle sedona@0.1.0~start: Args: [ '/d /s /c', 'npm run build && gulp serve' ]
11 silly lifecycle sedona@0.1.0~start: Returned: code: 3221225477  signal: null
12 info lifecycle sedona@0.1.0~start: Failed to exec start script
13 verbose stack Error: sedona@0.1.0 start: `npm run build && gulp serve`
13 verbose stack Exit status 3221225477
13 verbose stack     at EventEmitter.<anonymous> (D:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:289:16)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at EventEmitter.emit (events.js:213:7)
13 verbose stack     at ChildProcess.<anonymous> (D:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at ChildProcess.emit (events.js:213:7)
13 verbose stack     at maybeClose (internal/child_process.js:921:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid sedona@0.1.0
15 verbose cwd C:\Users\user\Desktop\user.github.io
16 verbose Windows_NT 6.1.7601
17 verbose argv "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.2.1
19 verbose npm  v5.3.0
20 error code ELIFECYCLE
21 error errno 3221225477
22 error sedona@0.1.0 start: `npm run build && gulp serve`
22 error Exit status 3221225477
23 error Failed at the sedona@0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225477, true ]

我已经从其他peolpe github下载了另一个gulp-sass项目，并将其包含在我自己的html-sass-js-img文件中.仍然错误，顺便说一句.

I have already downloaded another gulp-sass projects from other peolpe github's and replace it contains with my own html-sass-js-img files. Error still here btw.

我已经重新安装了cmder和node.js.两次.错误仍然存​​在.

I have already reinstall cmder and node.js. Twice. Error still here.

我已经从我的项目中删除了"node-modules"文件夹，并执行了"npm i"命令-没做任何更改.

I have already delete "node-modules" folder from my project and made "npm i" command - nothing changed.

一件有趣的事-文件夹"build"中的文件像往常一样更新(如果您像以前那样手动在浏览器中处理它们).但是在根文件夹中，好像gulp-sass只是什么都没有发生，并且在localhost 3000中显示零更改.

And one fun thing - files in folder "build" updated like always (if you manual lauch them in browser like in old times). But in root folder seems like gulp-sass just don't see that anything happen and zero changes displayed in localhost 3000.

我以前从昨天开始的构建工作正常(貌似)，而从github另一个人的构建工作也正常，但是为什么我的新构建进行了一些更改却导致崩溃?只会导致sass文件更改?

My previous build from yesterday work fine (seemingly) and builds from another people from github work fine too, but why my new build with some changes make that crash??? Only cause sass files changed?

推荐答案

因此，在使用Node 12.4.0进行调试时，在VSCode中的Jest中有一个有趣的原因.当运行jest和babel并将断点放置在静态类中时，第二次将它们放置在静态类中的静态方法中，node会引发此错误.要修复，请不要编写奇怪的静态类.

So, there's an interesting cause of this in Jest in VSCode while debugging with Node 12.4.0. When running jest and babel, and placing breakpoints in static classes, the second you place them in the static class, in a static method, node throws this error. To fix, dont write weird static classes.

这篇关于ELIFECYCLE npm错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！