npm / registry-issue-archive

An archive of the old npm registry issue tracker
https://npm.community
249 stars 47 forks source link

Cannot install private modules after fresh NPM login #374

Closed daveweber closed 6 years ago

daveweber commented 6 years ago

We've been having trouble downloading modules from our private registry ever since our tokens were reset as per the recent security incident. We're experiencing trouble both on our local environments, and remote testing environments provided by CircleCI. We authenticate using npm login, run npm install, and then observe the following output:

npm WARN notice Due to a recent security incident, all user tokens have been invalidated. Please see https://status.npmjs.org/incidents/dn7c1fgrr7ng for more details. To generate a new token, visit https://www.npmjs.com/settings/~/tokens or run "npm login".
npm http fetch GET 404 https://registry.npmjs.org/@shoelace%2ffacebook 459ms
npm WARN notice Due to a recent security incident, all user tokens have been invalidated. Please see https://status.npmjs.org/incidents/dn7c1fgrr7ng for more details. To generate a new token, visit https://www.npmjs.com/settings/~/tokens or run "npm login".
npm http fetch GET 404 https://registry.npmjs.org/@shoelace%2futils 461ms
npm ERR! code E404
npm ERR! 404 Not Found: @shoelace/facebook@1.149.0

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/circleci/.npm/_logs/2018-07-16T13_27_55_251Z-debug.log
daveweber commented 6 years ago

We're no longer seeing this issue