Bug #20232
closed
npm install fails
Description
npm install fails over here like:
$ npm install npm WARN package.json compression-webpack-plugin@0.3.2 No license field. npm WARN package.json events@1.1.1 events is also the name of a node core module. npm WARN package.json expose-loader@0.6.0 No license field. npm WARN package.json select2@3.5.2-browserify No license field. npm WARN package.json jquery-flot@0.8.3 No repository field. npm WARN package.json jquery-flot@0.8.3 No license field. npm WARN package.json jstz@1.0.9 No license field. npm WARN package.json multiselect@0.9.12 No repository field. Warning: Ignoring extra certs from `/etc/ssl/certs/ca-certificates.crt`, load failed: error:0B07C065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table npm ERR! 404 Not Found npm ERR! 404 npm ERR! 404 'storybook/react' is not in the npm registry. npm ERR! 404 You should bug the author to publish it npm ERR! 404 It was specified as a dependency of 'TheForemanDevDeps' npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, or http url, or git url. npm ERR! System Linux 4.9.0-3-amd64 npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" npm ERR! cwd /var/scratch/src/foreman/foreman npm ERR! node -v v4.8.3 npm ERR! npm -v 1.4.21 npm ERR! code E404 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /var/scratch/src/foreman/foreman/npm-debug.log npm ERR! not ok code 0
I'm unclear why it seems to work for everyone else.
Updated by Anonymous over 7 years ago
You should update to at least node 6.10.x and npm 4.x.
npm 5.x has also shown problems in the Debian package build, but works for my dev setup.
Updated by Anonymous over 7 years ago
- Related to Refactor #19512: update to node 6.10 as minimum node.js version added
Updated by Guido Günther over 7 years ago
- Status changed from New to Closed
Michael Moll wrote:
You should update to at least node 6.10.x and npm 4.x.
npm 5.x has also shown problems in the Debian package build, but works for my dev setup.
Makes sense. Closing then.
Updated by Guido Günther over 7 years ago
Guido Günther wrote:
Michael Moll wrote:
You should update to at least node 6.10.x and npm 4.x.
npm 5.x has also shown problems in the Debian package build, but works for my dev setup.
Makes sense. Closing then.
...the nodesource repos are not nie since they recommend "curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -" but it should rather help out on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772023(just as a data point that building on non EPEL isn't trivial atm).
Updated by Anonymous over 7 years ago
The main problem is Debian's lack of an usable npm in its repos (unless that changed in the last weeks).
The nodesource repos can also be added without curl|sh, of course, see e.g.
https://github.com/theforeman/foreman-infra/blob/185c62708d82638b3f03efc5f3019514fdb39afc/puppet/modules/debian/templates/pbuilder_f70.erb#L21
As an alternative to npm, yarn can be used: https://yarnpkg.com/ - in fact recent nightlies of Foreman do use yarn for the "npm install" step.
Updated by Guido Günther over 7 years ago
Michael Moll wrote:
The main problem is Debian's lack of an usable npm in its repos (unless that changed in the last weeks).
The nodesource repos can also be added without curl|sh, of course, see e.g.
https://github.com/theforeman/foreman-infra/blob/185c62708d82638b3f03efc5f3019514fdb39afc/puppet/modules/debian/templates/pbuilder_f70.erb#L21As an alternative to npm, yarn can be used: https://yarnpkg.com/ - in fact recent nightlies of Foreman do use yarn for the "npm install" step.
Yeah, that's all nice and thanks a lot for caring (honestly). I think my main point is that contributing to the foreman is non trivial if you only do it every once in a while since there are so many moving parts but I have little idea what to do about it besides running the steps from https://www.theforeman.org/contribute.html once a day on the "major" distros to see what breaks.