Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Error installing "forever" #679

Closed
googled opened this issue Jan 10, 2020 · 13 comments
Closed

[BUG] Error installing "forever" #679

googled opened this issue Jan 10, 2020 · 13 comments
Labels
Bug thing that needs fixing

Comments

@googled
Copy link

googled commented Jan 10, 2020

What / Why

@Dev-Ponged-Tracker:/home/ponged/nodejs/tracking# npm install forever -g
npm WARN deprecated [email protected]: This package is no longer relevant as Node.js 0.12 is unmaintained.
npm ERR! Linux 4.15.0-74-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "forever" "-g"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code EMISSINGARG

npm ERR! typeerror Error: Missing required argument #1
npm ERR! typeerror at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
npm ERR! typeerror at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
npm ERR! typeerror at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12)
npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
npm ERR! typeerror at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
npm ERR! typeerror at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
npm ERR! typeerror at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror This is an error with npm itself. Please report this error at:
npm ERR! typeerror http://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! /home/ponged/nodejs/tracking/npm-debug.log
root@Dev-Ponged-Tracker:/home/ponged/nodejs/tracking#
npm-debug.log

@DanielRuf
Copy link

npm ERR! npm v3.5.2

You are using a totally oudated npm version. Please upgrade to npm 6.

@ljharb
Copy link
Contributor

ljharb commented Jan 14, 2020

This is the same error as #681, which seems to be a recent registry change breaking older clients that used to work just fine.

@googled
Copy link
Author

googled commented Jan 14, 2020

Well, it's still the current official apt Ubuntu 18 version.

It's a breaking change, should be fixed.

@DanielRuf
Copy link

Did you already try npm i -g npm@latest?

@googled
Copy link
Author

googled commented Jan 14, 2020

Never occurred to me to npm@latest, the javascript package manager, besides packages inside a project. Thank you for the tip!

tl;dr

Though I now rely on pm2 instead of forever which is far more advanced.

@DanielRuf
Copy link

I'm not sure I can follow.

Does the issue still occur with the latest npm version?

@googled
Copy link
Author

googled commented Jan 14, 2020

Couple deprecated WARN but it installed.

@DanielRuf
Copy link

Then it should be resolved =)

@discapacidad5
Copy link

I have the same ubuntu 18.4 problem

@DanielRuf
Copy link

@discapacidad5 please open a new issue, provide all details about the error that you see and provide some information about your node version and npm version.

@darcyclarke darcyclarke added the Bug thing that needs fixing label Oct 30, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

2 similar comments
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing
Projects
None yet
Development

No branches or pull requests

5 participants