<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 000003E0EA7A57C1 <JSObject>
1: new constructor(aka Buffer) [buffer.js:~147] [pc=0000011D15D7EA21](this=0000038EF8E14AB9 <Buffer map = 0000007E6784A1E9>,arg=0000038EF8E14A91 <Very long string[11171091]>,encodingOrOffset=000003E0EA7B4EB1 <String[4]: utf8>,length=0000009874E022D1 <undefined>)
2: arguments adaptor frame: 2->3
5: writeOut(aka writeOut) [E:\systemDirectory\test\node_modules\_webpack@3.11.0@webpack\...
這個(gè)是報(bào)錯(cuò)信息, 請(qǐng)各路大神給點(diǎn)提示, 非常感謝
新錯(cuò)誤
換了一個(gè)錯(cuò)誤了.
0 info it worked if it ends with ok
1 verbose cli [ 'D:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\ThinkPad\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm@5.7.1
3 info using node@v8.10.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle wisdomfire@1.0.0~prestart: wisdomfire@1.0.0
6 info lifecycle wisdomfire@1.0.0~start: wisdomfire@1.0.0
7 verbose lifecycle wisdomfire@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle wisdomfire@1.0.0~start: PATH: C:\Users\ThinkPad\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\systemDirectory\test\node_modules\.bin;C:\Users\ThinkPad\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\local\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\bin;C:\Users\ThinkPad\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;D:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;D:\Program Files\nodejs;C:\Users\ThinkPad\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\ThinkPad\AppData\Roaming\npm;D:\Program Files\Git\usr\bin\vendor_perl;D:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle wisdomfire@1.0.0~start: CWD: E:\systemDirectory\test
10 silly lifecycle wisdomfire@1.0.0~start: Args: [ '/d /s /c', 'npm run dev' ]
11 silly lifecycle wisdomfire@1.0.0~start: Returned: code: 3 signal: null
12 info lifecycle wisdomfire@1.0.0~start: Failed to exec start script
13 verbose stack Error: wisdomfire@1.0.0 start: `npm run dev`
13 verbose stack Exit status 3
13 verbose stack at EventEmitter.<anonymous> (C:\Users\ThinkPad\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\ThinkPad\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid wisdomfire@1.0.0
15 verbose cwd E:\systemDirectory\test
16 verbose Windows_NT 10.0.16299
17 verbose argv "D:\\Program Files\\nodejs\\node.exe" "C:\\Users\\ThinkPad\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.10.0
19 verbose npm v5.7.1
20 error code ELIFECYCLE
21 error errno 3
22 error wisdomfire@1.0.0 start: `npm run dev`
22 error Exit status 3
23 error Failed at the wisdomfire@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3, true ]
舊錯(cuò)誤
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.5.1
3 info using node@v9.3.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle widsomfire@1.0.0~prestart: widsomfire@1.0.0
6 info lifecycle widsomfire@1.0.0~start: widsomfire@1.0.0
7 verbose lifecycle widsomfire@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle widsomfire@1.0.0~start: PATH: D:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;E:\systemDirectory\test\node_modules\.bin;C:\Users\ThinkPad\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\local\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\bin;C:\Users\ThinkPad\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;D:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;D:\Program Files\nodejs;C:\Users\ThinkPad\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\ThinkPad\AppData\Roaming\npm;D:\Program Files\Git\usr\bin\vendor_perl;D:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle widsomfire@1.0.0~start: CWD: E:\systemDirectory\test
10 silly lifecycle widsomfire@1.0.0~start: Args: [ '/d /s /c', 'npm run dev' ]
11 silly lifecycle widsomfire@1.0.0~start: Returned: code: 134 signal: null
12 info lifecycle widsomfire@1.0.0~start: Failed to exec start script
13 verbose stack Error: widsomfire@1.0.0 start: `npm run dev`
13 verbose stack Exit status 134
13 verbose stack at EventEmitter.<anonymous> (D:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack at EventEmitter.emit (events.js:159:13)
13 verbose stack at ChildProcess.<anonymous> (D:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:159:13)
13 verbose stack at maybeClose (internal/child_process.js:943:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid widsomfire@1.0.0
15 verbose cwd E:\systemDirectory\test
16 verbose Windows_NT 10.0.16299
17 verbose argv "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v9.3.0
19 verbose npm v5.5.1
20 error code ELIFECYCLE
21 error errno 134
22 error widsomfire@1.0.0 start: `npm run dev`
22 error Exit status 134
23 error Failed at the widsomfire@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 134, true ]
整了幾天, 原因是熱更新時(shí) string 過(guò)大, 導(dǎo)致內(nèi)存溢出了, 解決辦法是在 package.json 的 script 中加大 node 的運(yùn)行內(nèi)存. 解決方法如下↓
"scripts": {
"dev": "node --max-old-space-size=6000 ./node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --progress --config build/webpack.dev.conf.js",
"start": "npm run dev",
}
北大青鳥(niǎo)APTECH成立于1999年。依托北京大學(xué)優(yōu)質(zhì)雄厚的教育資源和背景,秉承“教育改變生活”的發(fā)展理念,致力于培養(yǎng)中國(guó)IT技能型緊缺人才,是大數(shù)據(jù)專業(yè)的國(guó)家
北大青鳥(niǎo)中博軟件學(xué)院創(chuàng)立于2003年,作為華東區(qū)著名互聯(lián)網(wǎng)學(xué)院和江蘇省首批服務(wù)外包人才培訓(xùn)基地,中博成功培育了近30000名軟件工程師走向高薪崗位,合作企業(yè)超4
中公教育集團(tuán)創(chuàng)建于1999年,經(jīng)過(guò)二十年潛心發(fā)展,已由一家北大畢業(yè)生自主創(chuàng)業(yè)的信息技術(shù)與教育服務(wù)機(jī)構(gòu),發(fā)展為教育服務(wù)業(yè)的綜合性企業(yè)集團(tuán),成為集合面授教學(xué)培訓(xùn)、網(wǎng)
達(dá)內(nèi)教育集團(tuán)成立于2002年,是一家由留學(xué)海歸創(chuàng)辦的高端職業(yè)教育培訓(xùn)機(jī)構(gòu),是中國(guó)一站式人才培養(yǎng)平臺(tái)、一站式人才輸送平臺(tái)。2014年4月3日在美國(guó)成功上市,融資1
曾工作于聯(lián)想擔(dān)任系統(tǒng)開(kāi)發(fā)工程師,曾在博彥科技股份有限公司擔(dān)任項(xiàng)目經(jīng)理從事移動(dòng)互聯(lián)網(wǎng)管理及研發(fā)工作,曾創(chuàng)辦藍(lán)懿科技有限責(zé)任公司從事總經(jīng)理職務(wù)負(fù)責(zé)iOS教學(xué)及管理工作。
浪潮集團(tuán)項(xiàng)目經(jīng)理。精通Java與.NET 技術(shù), 熟練的跨平臺(tái)面向?qū)ο箝_(kāi)發(fā)經(jīng)驗(yàn),技術(shù)功底深厚。 授課風(fēng)格 授課風(fēng)格清新自然、條理清晰、主次分明、重點(diǎn)難點(diǎn)突出、引人入勝。
精通HTML5和CSS3;Javascript及主流js庫(kù),具有快速界面開(kāi)發(fā)的能力,對(duì)瀏覽器兼容性、前端性能優(yōu)化等有深入理解。精通網(wǎng)頁(yè)制作和網(wǎng)頁(yè)游戲開(kāi)發(fā)。
具有10 年的Java 企業(yè)應(yīng)用開(kāi)發(fā)經(jīng)驗(yàn)。曾經(jīng)歷任德國(guó)Software AG 技術(shù)顧問(wèn),美國(guó)Dachieve 系統(tǒng)架構(gòu)師,美國(guó)AngelEngineers Inc. 系統(tǒng)架構(gòu)師。