clone has a node+react framework and intends to learn server-side rendering, but npm install cannot start it after installing dependencies. Here is Debug.log
0 info it worked if it ends with ok
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 "start" ]
2 info using npm@5.3.0
3 info using node@v8.4.0
4 verbose run-script [ "prestart", "start", "poststart" ]
5 info lifecycle funsee-boilerplate@1.0.0~prestart: funsee-boilerplate@1.0.0
6 info lifecycle funsee-boilerplate@1.0.0~start: funsee-boilerplate@1.0.0
7 verbose lifecycle funsee-boilerplate@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle funsee-boilerplate@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;D:\myoss-node-wechat-master\node-wechat\node_modules\.bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files (x86)\Razer Chroma SDK\bin;C:\Program Files\Razer Chroma SDK\bin;C:\Program Files\Intel\iCLS Client\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\nodejs\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Users\13272\AppData\Local\Microsoft\WindowsApps;C:\Users\13272\AppData\Roaming\npm;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Users\13272\AppData\Local\Microsoft\WindowsApps;C:\Users\13272\AppData\Roaming\npm;
9 verbose lifecycle funsee-boilerplate@1.0.0~start: CWD: D:\myoss-node-wechat-master\node-wechat
10 silly lifecycle funsee-boilerplate@1.0.0~start: Args: [ "/d /s /c", "funsee-hammer start" ]
11 silly lifecycle funsee-boilerplate@1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle funsee-boilerplate@1.0.0~start: Failed to exec start script
13 verbose stack Error: funsee-boilerplate@1.0.0 start: `funsee-hammer start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\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> (C:\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:927:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid funsee-boilerplate@1.0.0
15 verbose cwd D:\myoss-node-wechat-master\node-wechat
16 verbose Windows_NT 10.0.16299
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
18 verbose node v8.4.0
19 verbose npm v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error funsee-boilerplate@1.0.0 start: `funsee-hammer start`
22 error Exit status 1
23 error Failed at the funsee-boilerplate@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 [ 1, true ]
hope to get an answer, and hope to get a way to solve the problem, thank you!