這發生在節點版本 14.16.0 上。我現在遇到了兩次錯誤。我第一次使用@mui/lab/DateTimePicker 創建了一個反應組件。
我不必安裝它,因為 @mui/lab 已經存在于專案中。(試圖在另一個分支上重現這個(除了很少的變化)。沒有作業,所以可能與 mui 本身無關)
第二次也是時間輸入組件的第二種方法。使用我這次必須安裝的另一個更簡單的節點模塊。(也無法重現這種情況)(第二次像魅力一樣作業)
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from C:\develop\strapi-nextjs-poc\nextjs\.env
info - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
event - compiled successfully in 5.7s (2008 modules)
wait - compiling /...
info - Using external babel configuration from C:\develop\strapi-nextjs-poc\nextjs\.babelrc
[styled-jsx] Loading plugin from path: C:\develop\strapi-nextjs-poc\nextjs\node_modules\@styled-jsx\plugin-sass\index.js
event - compiled successfully in 6.9s (2236 modules)
npm ERR! code ELIFECYCLE
npm ERR! errno 3221225477
npm ERR! nextjs@0.1.0 dev: `next dev`
npm ERR! Exit status 3221225477
npm ERR!
npm ERR! Failed at the nextjs@0.1.0 dev 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\sk\AppData\Roaming\npm-cache\_logs\2022-02-17T12_52_28_233Z-debug.log
/c/Program Files/nodejs/npm: line 37: 3732 Segmentation fault "$NODE_EXE" "$NPM_CLI_JS" "$@"
可悲的是,恢復當前的更改并沒有做任何事情。即使洗掉了自上次作業提交以來的所有更改,分支仍然損壞。
到目前為止我嘗試了什么(按此順序):
- 從源代碼和包 json 中洗掉依賴項(剛剛洗掉了自上次作業提交以來的所有內容)
- 洗掉 .nextjs 檔案夾(用于快取)
- 洗掉了 node_modules 檔案夾
- 使用 nvm 洗掉當前節點版本并重新安裝
npm cache clean --forcenpm install
在遇到錯誤一次之后,它似乎是分支上的一個永久性問題(即使對于其他人來說也是如此)。所以分支基本上不再可用了。
我發現修復錯誤復發的唯一方法是升級節點。用v14.19.0試過,
這只是帶來了專案中node版本可能出現的其他問題。
有什么想法為什么會發生這種情況,是什么原因造成的,或者什么可以解決它?
完整日志:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev'
1 verbose cli ]
2 info using npm@6.14.11
3 info using node@v14.16.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle nextjs@0.1.0~predev: nextjs@0.1.0
6 info lifecycle nextjs@0.1.0~dev: nextjs@0.1.0
7 verbose lifecycle nextjs@0.1.0~dev: unsafe-perm in lifecycle true
8 verbose lifecycle nextjs@0.1.0~dev: PATH: C:\Users\sk\AppData\Roaming\nvm\v14.16.0\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\develop\strapi-nextjs-poc\nextjs\node_modules\.bin;C:\Users\sk\bin;C:\Users\sk\AppData\Local\Programs\Git\mingw64\bin;C:\Users\sk\AppData\Local\Programs\Git\usr\local\bin;C:\Users\sk\AppData\Local\Programs\Git\usr\bin;C:\Users\sk\AppData\Local\Programs\Git\usr\bin;C:\Users\sk\AppData\Local\Programs\Git\mingw64\bin;C:\Users\sk\AppData\Local\Programs\Git\usr\bin;C:\Users\sk\bin;C:\Python39\Scripts;C:\Python39;C:\Program Files\Zulu\zulu11.35.13-ca-jdk11.0.5-win_x64\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python38\Scripts;C:\Python38;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Users\adminal\.jpm\windows\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\MySQL\MySQL Server 5.7\bin;C:\Users\sk\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\sk\AppData\Local\Microsoft\WindowsApps;C:\Users\sk\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\sk\AppData\Local\Programs\Git\usr\bin\vendor_perl;C:\Users\sk\AppData\Local\Programs\Git\usr\bin\core_perl
9 verbose lifecycle nextjs@0.1.0~dev: CWD: C:\develop\strapi-nextjs-poc\nextjs
10 silly lifecycle nextjs@0.1.0~dev: Args: [ '/d /s /c', 'next dev' ]
11 silly lifecycle nextjs@0.1.0~dev: Returned: code: 3221225477 signal: null
12 info lifecycle nextjs@0.1.0~dev: Failed to exec dev script
13 verbose stack Error: nextjs@0.1.0 dev: `next dev`
13 verbose stack Exit status 3221225477
13 verbose stack at EventEmitter.<anonymous> (C:\Users\sk\AppData\Roaming\nvm\v14.16.0\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\sk\AppData\Roaming\nvm\v14.16.0\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid nextjs@0.1.0
15 verbose cwd C:\develop\strapi-nextjs-poc\nextjs
16 verbose Windows_NT 10.0.19042
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
18 verbose node v14.16.0
19 verbose npm v6.14.11
20 error code ELIFECYCLE
21 error errno 3221225477
22 error nextjs@0.1.0 dev: `next dev`
22 error Exit status 3221225477
23 error Failed at the nextjs@0.1.0 dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225477, true ]
uj5u.com熱心網友回復:
基于錯誤代碼 - 它看起來像一個 win32 訪問沖突錯誤,詳見
轉載請註明出處,本文鏈接:https://www.uj5u.com/shujuku/428352.html
上一篇:反應渲染不顯示任何東西
下一篇:NPM安裝失敗,OSX
