Failing when trying to run 'npm run build'

I am using v3.0.8 and I am running into issues when I am trying to build swagger-ui with my changes. I have included the npm-debug log, as well as some of the dependencies that npm had said were deprecated when installing npm.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/bin/npm', 'run', 'build' ]
2 info using npm@3.10.10
3 info using node@v6.10.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle swagger-ui@3.0.8~prebuild: swagger-ui@3.0.8
6 silly lifecycle swagger-ui@3.0.8~prebuild: no script for prebuild, continuing
7 info lifecycle swagger-ui@3.0.8~build: swagger-ui@3.0.8
8 verbose lifecycle swagger-ui@3.0.8~build: unsafe-perm in lifecycle true
9 verbose lifecycle swagger-ui@3.0.8~build: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/var/www/swagger-ui/releases/3.0.8/node_modules/.bin:/usr/bin:/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/bin/
10 verbose lifecycle swagger-ui@3.0.8~build: CWD: /var/www/swagger-ui/releases/3.0.8
11 silly lifecycle swagger-ui@3.0.8~build: Args: [ '-c',
11 silly lifecycle   'npm run build-core && npm run build-bundle && npm run build-standalone' ]
12 silly lifecycle swagger-ui@3.0.8~build: Returned: code: 1  signal: null
13 info lifecycle swagger-ui@3.0.8~build: Failed to exec build script
14 verbose stack Error: swagger-ui@3.0.8 build: `npm run build-core && npm run build-bundle && npm run build-standalone`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/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.<anonymous> (/usr/lib/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:886:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid swagger-ui@3.0.8
16 verbose cwd /var/www/swagger-ui/releases/3.0.8
17 error Linux 3.10.0-514.10.2.el7.x86_64
18 error argv "/usr/bin/node" "/bin/npm" "run" "build"
19 error node v6.10.1
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error swagger-ui@3.0.8 build: `npm run build-core && npm run build-bundle && npm run build-standalone`
22 error Exit status 1
23 error Failed at the swagger-ui@3.0.8 build script 'npm run build-core && npm run build-bundle && npm run build-standalone'.
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 swagger-ui package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     npm run build-core && npm run build-bundle && npm run build-standalone
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs swagger-ui
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls swagger-ui
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Modules that NPM says are deprecated:

babel-plugin-module-alias@1.6.0
to-iso-string@0.0.2
jade@0.26.3
minimatch@0.3.0

There was also output saying npm-gyp should be installed globally (not sure if that is something I should do since I am not running npm on windows and some warning NPM gave me after the install:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”}) npm WARN react-addons-shallow-compare@0.14.8 requires a peer of react@^0.14.8 but none was installed. npm WARN react-addons-perf@0.14.8 requires a peer of react@^0.14.8 but none was installed. npm WARN react-object-inspector@0.2.1 requires a peer of react@^0.14.0 but none was installed. npm WARN sass-loader@6.0.3 requires a peer of webpack@^2.0.0 but none was installed. npm WARN eslint-config-standard-jsx@3.2.0 requires a peer of eslint@>=3.0.0 but none was installed. npm WARN eslint-config-standard@6.2.1 requires a peer of eslint@>=3.8.1 but none was installed. npm WARN eslint-plugin-standard@2.0.1 requires a peer of eslint@>=3.0.0 but none was installed.

I am putting this in the google group as well as here, and either one can be removed if it feels redundant. Thank you for any help you can provide!

[tylerjames]

@shockey I was able to get it to work. At first I had downloaded a zip of the repo. In that case I experienced the problems I described. When I instead cloned the repo the npm install worked fine. It seemed to not like that it didn’t reside in an existing git repo.

[tylerjames]

@shockey That seems to have fixed it