Can't `npm install`

[vivienm]

Been trying to install the (freshly cloned) repository, as per https://github.com/Accedian/datahub-api#install:

$ pwd
/home/vivien/accedian/projects/datahub-api
$ git clean -fxd
$ git pull
Already up to date.
$ git branch
* master
$ npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated natives@1.1.4: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated formidable@1.2.1: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated source-map-resolve@0.5.2: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated connect@2.30.2: connect 2.x series is deprecated
npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. Thanks to @shadowgate15, @spence-s, and @niftylettuce. Superagent is sponsored by Forward Email at <https://forwardemail.net>.
npm WARN deprecated swagger-ui@2.2.10: No longer maintained, please upgrade to swagger-ui@3.
npm WARN deprecated core-js@2.6.9: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.9: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@3.2.1: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated swagger-editor@2.10.5: No longer maintained, please upgrade to swagger-editor@3.
npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
npm ERR! code 1
npm ERR! path /home/vivien/accedian/projects/datahub-api/node_modules/install-peers
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! Unable to install peerDependencies Error: Command failed: "/usr/bin/node" "/usr/lib/node_modules/npm/bin/npm-cli.js" install --no-save --no-package-lock "core-js@^3.1.4" "mobx@^4.2.0 || ^5.0.0" "react@^16.8.4" "react-dom@^16.8.4" "styled-components@^4.1.1"
npm ERR! npm WARN idealTree Removing peerDependencies.mobx in favor of dependencies.mobx
npm ERR! npm ERR! code ERESOLVE
npm ERR! npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! npm ERR!
npm ERR! npm ERR! While resolving: Skylight-openapi-spec@2.0.0
npm ERR! npm ERR! Found: mobx@5.15.7
npm ERR! npm ERR! node_modules/mobx
npm ERR! npm ERR!   mobx@"^4.2.0 || ^5.0.0" from the root project
npm ERR! npm ERR!
npm ERR! npm ERR! Could not resolve dependency:
npm ERR! npm ERR! peer mobx@"^6.0.4" from redoc@2.0.0-rc.59
npm ERR! npm ERR! node_modules/redoc
npm ERR! npm ERR!   redoc@"^2.0.0-rc.14" from the root project
npm ERR! npm ERR!
npm ERR! npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! npm ERR!
npm ERR! npm ERR! See /home/vivien/.npm/eresolve-report.txt for a full report.
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR!     /home/vivien/.npm/_logs/2022-01-12T10_41_53_460Z-debug-0.log
npm ERR!     at ChildProcess.exithandler (node:child_process:397:12)
npm ERR!     at ChildProcess.emit (node:events:390:28)
npm ERR!     at maybeClose (node:internal/child_process:1062:16)
npm ERR!     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {
npm ERR!   killed: false,
npm ERR!   code: 1,
npm ERR!   signal: null,
npm ERR!   cmd: '"/usr/bin/node" "/usr/lib/node_modules/npm/bin/npm-cli.js" install --no-save --no-package-lock "core-js@^3.1.4" "mobx@^4.2.0 || ^5.0.0" "react@^16.8.4" "react-dom@^16.8.4" "styled-components@^4.1.1"',
npm ERR!   stdout: '',
npm ERR!   stderr: 'npm WARN idealTree Removing peerDependencies.mobx in favor of dependencies.mobx\n' +
npm ERR!     'npm ERR! code ERESOLVE\n' +
npm ERR!     'npm ERR! ERESOLVE unable to resolve dependency tree\n' +
npm ERR!     'npm ERR! \n' +
npm ERR!     'npm ERR! While resolving: Skylight-openapi-spec@2.0.0\n' +
npm ERR!     'npm ERR! Found: mobx@5.15.7\n' +
npm ERR!     'npm ERR! node_modules/mobx\n' +
npm ERR!     'npm ERR!   mobx@"^4.2.0 || ^5.0.0" from the root project\n' +
npm ERR!     'npm ERR! \n' +
npm ERR!     'npm ERR! Could not resolve dependency:\n' +
npm ERR!     'npm ERR! peer mobx@"^6.0.4" from redoc@2.0.0-rc.59\n' +
npm ERR!     'npm ERR! node_modules/redoc\n' +
npm ERR!     'npm ERR!   redoc@"^2.0.0-rc.14" from the root project\n' +
npm ERR!     'npm ERR! \n' +
npm ERR!     'npm ERR! Fix the upstream dependency conflict, or retry\n' +
npm ERR!     'npm ERR! this command with --force, or --legacy-peer-deps\n' +
npm ERR!     'npm ERR! to accept an incorrect (and potentially broken) dependency resolution.\n' +
npm ERR!     'npm ERR! \n' +
npm ERR!     'npm ERR! See /home/vivien/.npm/eresolve-report.txt for a full report.\n' +
npm ERR!     '\n' +
npm ERR!     'npm ERR! A complete log of this run can be found in:\n' +
npm ERR!     'npm ERR!     /home/vivien/.npm/_logs/2022-01-12T10_41_53_460Z-debug-0.log'
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vivien/.npm/_logs/2022-01-12T10_41_45_912Z-debug-0.log

Versions:

$ node --version
v17.3.0
$ npm --version
8.3.0

[sglanzer]

Giving this a try now, I'll post back results

[sglanzer]

I can see the same issue locally, I'll check the dependencies and try to get this resolved

[sglanzer]

The referenced PR should fix the peer dependency, but this only appears to run in node 10 or below (probably something like a 6-10 range). I'd use a node version manager like https://github.com/tj/n to set your node version to 10 and then you'll be able to build

[vivienm]

Got it, thanks. FYI Node 10 is EOL since april 2021: https://nodejs.org/ru/blog/release/v10.13.0/.

[sglanzer]

Yeah, I think we’d all agree the docs solution is well outdated - there is a round tool evaluation ongoing for that

On Fri, Jan 14, 2022 at 1:18 AM Vivien Maisonneuve ***@***.***> wrote: Ok. FYI Node 10 is EOL since april 2021: https://nodejs.org/ru/blog/release/v10.13.0/. — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHT3FMWUKTLJQ4FZKFVYKRDUV653LANCNFSM5LYUC3PA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- *Steven Glanzer* *Manager UI, Network Performance Analytics and Visualization* 1.866.685.8181 ***@***.*** <http://accedian.com> <https://www.facebook.com/accedian/> <https://twitter.com/Accedian> <https://ca.linkedin.com/company/accedian> <http://www.accedian.com> *accedian.com <http://accedian.com>*

…

-- Avis de confidentialité Les informations contenues dans le présent message et dans toute pièce qui lui est jointe sont confidentielles et peuvent être protégées par le secret professionnel. Ces informations sont à l’usage exclusif de son ou de ses destinataires. Si vous recevez ce message par erreur, veuillez s’il vous plait communiquer immédiatement avec l’expéditeur et en détruire tout exemplaire. De plus, il vous est strictement interdit de le divulguer, de le distribuer ou de le reproduire sans l’autorisation de l’expéditeur. Merci. Confidentiality notice This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.