1. A concise explanation of the problem you’re experiencing.
Attempting to run npm run build and can not continue past.
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
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 ‘build’ ]
2 info using npm@3.10.10
3 info using node@v6.11.3
4 verbose run-script [ ‘prebuild’, ‘build’, ‘postbuild’ ]
5 info lifecycle cesium@1.37.0~prebuild: cesium@1.37.0
6 silly lifecycle cesium@1.37.0~prebuild: no script for prebuild, continuing
7 info lifecycle cesium@1.37.0~build: cesium@1.37.0
8 verbose lifecycle cesium@1.37.0~build: unsafe-perm in lifecycle true
9 verbose lifecycle cesium@1.37.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Cesium\node_modules.bin;C:\Program Files\Trend Micro\AMSP;C:\Program Files (x86)\Razer Chroma SDK\bin;C:\Program Files\Razer Chroma SDK\bin;C:\ProgramData\Oracle\Java\javapath;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\MATLAB\R2013b\runtime\win64;C:\Program Files\MATLAB\R2013b\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Users\zacha\AppData\Local\Microsoft\WindowsApps;C:\Program Files\nodejs;C:\Users\zacha\AppData\Local\Microsoft\WindowsApps;C:\Users\zacha\AppData\Roaming\npm
10 verbose lifecycle cesium@1.37.0~build: CWD: C:\Cesium
11 silly lifecycle cesium@1.37.0~build: Args: [ ‘/d /s /c’, ‘gulp build’ ]
12 silly lifecycle cesium@1.37.0~build: Returned: code: 1 signal: null
13 info lifecycle cesium@1.37.0~build: Failed to exec build script
14 verbose stack Error: cesium@1.37.0 build: gulp build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:920:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid cesium@1.37.0
16 verbose cwd C:\Cesium
17 error Windows_NT 10.0.15063
18 error argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” “run” “build”
19 error node v6.11.3
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error cesium@1.37.0 build: gulp build
22 error Exit status 1
23 error Failed at the cesium@1.37.0 build script ‘gulp build’.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the cesium package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error gulp build
23 error You can get information on how to open an issue for this project with:
23 error npm bugs cesium
23 error Or if that isn’t available, you can get their info via:
23 error npm owner ls cesium
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
4. The Cesium version you’re using, your operating system and browser.
Cesium 1.37, Windows 10 Pro, Google Chrome Version 61.0.3163.100