Hi
When I tried to install pm2 via npm I am getting npm ERR! code E404
The command I ran npm i pm2 -g
Output :
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@pm2%2fagent - Not found
npm ERR! 404
npm ERR! 404 '@pm2/agent@~1.0.2' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'pm2'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2020-08-06T09_50_56_130Z-debug.log
$ pm2 report
same here
Getting a similar error, but for version check:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm-registry.westwing.eu/repository/npm/@pm2%2fpm2-version-check - Not found
npm ERR! 404
npm ERR! 404 '@pm2/[email protected]' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-08-06T10_00_28_545Z-debug.log
I see a similar error, but it sometimes shows http://registry.npmjs.org/@pm2%2fagent as not found, and sometimes https://registry.npmjs.org/@pm2%2fio
I'm having the same issue, trying to install pm2 - 4.4.0
I even try to install, "pm2": "~4.1.2" and got the same error
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@pm2%2fjs-api - Not found
npm ERR! 404
npm ERR! 404 '@pm2/js-api@~0.6.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'pm2'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
Same here from last 1 hour.
Please fix this ASAP this is a showstopper for alot of organizations
Tried again and it worked.
cay
Gonna try again now
Tried again and it worked.
is working now, bizarre!
Seems like an issue with NPM cache.
closing at it was related to npm
Most helpful comment
Tried again and it worked.