-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
are-we-there-yet #4529
Comments
A more specific bug report would help, just "an error" is too vague. Can you post the exact steps you've taken and the output you get? |
Totally inadequate bug report. @Gert25 Start over. What is "an error". |
I'm pretty sure this is related to #3540, #3606 and a few others. are-we-there-yet was one of the modules that showed up as evidence of the problem, but not the cause of it. Basically npm changed dramatically between version 2 and 3 and what's in /usr/local/lib/node_modules/npm (or perhaps another location depending on how you installed Node and on what platform) is a mix of old and new npm files when you upgrade from one version to the other. The easiest solution is to delete that directory completely, |
Hi George Sorry should not post on stack overflow when I am frustrated. I fixed the Regards On Tue, Jan 5, 2016 at 3:30 PM, George Bailey [email protected]
|
Soooo..... How did you fix the problem? |
As mentioned above
|
Trying to install newer version of npm from older version causes an error. Even reinstalling the latest version of node.js does not seem to work.
The text was updated successfully, but these errors were encountered: