npm upgrade destroyed npm

[tad]

I just tried to upgrade to the latest npm by doing:

npm install npm -g

And that threw a bunch of errors, and now npm is busted.

Do I need to reinstall node?

[tad]

I have since closed that terminal window (dumb, I know) so I can't share the errors that were thrown.

They all mostly looked like access/permissions errors.

I haven't had any problems with npm in the past.

[tad]

I found this:

workshopper/how-to-npm#27

Apparently that one npm install requires to be run via sudo. I've installed tons of other npm modules globally without sudo, but I guess from now on I'll always use sudo.

[tad]

I did reinstall node and then I was able to successfully upgrade npm by using sudo.

[stonemirror]

On Jul 31, 2015, at 11:13 AM, Tad Donaghe [email protected] wrote:

I found this:

workshopper/how-to-npm#27

Apparently that one npm install requires to be run via sudo. I've installed tons of other npm modules globally without sudo, but I guess from now on I'll always use sudo.

In my experience, any global (i.e. "-g") install needs escalated privileges.

[SomeoneWeird]

You should never upgrade npm by running npm upgrade npm, you should always do npm install npm@latest -g