I just tried removing the node_modules folder, clearing my npm cache, and running the commands again, I had noticed there were some deprecated dependencies in the package.json file. Here is a list of all that I have seen that are deprecated:
[email protected] [email protected] [email protected] [email protected] 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 Here is what was output at the end of the npm 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 [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN [email protected] requires a peer of react@^0.14.8 but none was installed. npm WARN [email protected] requires a peer of react@^0.14.8 but none was installed. npm WARN [email protected] requires a peer of react@^0.14.0 but none was installed. npm WARN [email protected] requires a peer of webpack@^2.0.0 but none was installed. npm WARN [email protected] requires a peer of eslint@>=3.0.0 but none was installed. npm WARN [email protected] requires a peer of eslint@>=3.8.1 but none was installed. npm WARN [email protected] requires a peer of eslint@>=3.0.0 but none was installed. On Thursday, May 4, 2017 at 10:31:23 AM UTC-6, Nick wrote: > > I am following the documentation in how to build after making changes to > swagger-ui, but npm tells me there is an error. I am running swagger-ui on > centos 7. Npm also told me to include this file, which is the npm-debug log: > > 0 info it worked if it ends with ok > 1 verbose cli [ '/usr/bin/node', '/bin/npm', 'run', 'build' ] > 2 info using [email protected] > 3 info using [email protected] > 4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] > 5 info lifecycle [email protected]~prebuild: [email protected] > 6 silly lifecycle [email protected]~prebuild: no script for prebuild, > continuing > 7 info lifecycle [email protected]~build: [email protected] > 8 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true > 9 verbose lifecycle [email protected]~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 [email protected]~build: CWD: > /var/www/swagger-ui/releases/3.0.8 > 11 silly lifecycle [email protected]~build: Args: [ '-c', > 11 silly lifecycle 'npm run build-core && npm run build-bundle && npm > run build-standalone' ] > 12 silly lifecycle [email protected]~build: Returned: code: 1 signal: null > 13 info lifecycle [email protected]~build: Failed to exec build script > 14 verbose stack Error: [email protected] 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 [email protected] > 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 [email protected] build: `npm run build-core && npm run > build-bundle && npm run build-standalone` > 22 error Exit status 1 > 23 error Failed at the [email protected] 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 ] > > If you need any more information, I can provide it, and any help is > appreciated! > -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
