The first test nukes NPM

[abjbhat]

I ran how-to-npm verify for the very first test. When the tool/test found that I have an out of date version, it reported it as so. Of course, after that, I could not find npm on bash. I can verify that npm was installed, because that's how I installed how-to-npm in the first place. sudo or not, it nukes my npm install every time.

I had to reinstall node each time get things working again. Thanks a lot, how-to-npm!

My system details OS X 10.10.3 Node v0.12.4

[ericmarkmartin]

Did you execute npm install npm -g?

On OS X, because a global install modifies /usr/local/lib, you need root permissions to install globally. Thus, when you try to install npm globally with npm without privilege, it removes your version and goes to get the new one, only to find it can't install it globally (doesn't have adequate permissions). The easy fix is to instead run sudo npm install npm -g. It will prompt you to type in your password (your password will not show up in the terminal window, but don't worry, it's there) and you'll be golden. You usually have to use sudo to install any module globally with npm on OS X.

[abjbhat]

Eric,

Each time that I ran how-to-npm verify, npm would vanish from my system. I had to rerun the node dpkg installer to get npm back after attempting the first test.

[tad]

Eric - I had this problem as well - nuked my node installation when I tried to

npm install npm -g

I didn't do sudo, but I've installed plenty of other npm modules without using sudo. Why is this different?

[claudiopro]

+1, happened to me also. Luckily I had just installed 4.0.0 :grin: