补充: 应该是编译时内存溢出的原因, 但是在网上没找到相关资料在开发项目时设置内存的方法.

<--- 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\...

这个是报错信息, 请各路大神给点提示, 非常感谢
新错误

换了一个错误了.

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 ]

旧错误

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 ]