Reboot (or you probably can get away with killing all node-related processes from Task Manager).Uninstalled NodeJS from Programs & Features with the uninstaller.Note: I've used the Microsoft automated script in the past to fix this, but only because I didn't realize how easy it would be to do it myself.Īll npm install commands were getting stuck and will throw error (behind proxy error) after sometime. Re-add Node (in Program Files)/NPM (in App Data - the one installed in Program Files should be the old one) to your user and system environment variables.If this solution would work for you, step 4 would have worked, and npm -v will show a an up-to-date version.
Run from the console in %USERPROFILE%, "C:\Program Files\nodejs\npm" install npm -g (you might have yours in the x86 folder).Change directories to %USERPROFILE% - that's a window's environment variable that takes you to C:\Users\CurrentlyLoggedInUser.Close your open console if you have one open, then open a console as administrator.Remove NPM/Node from your Environment Variables, both for user and system.After a bit of playing around, this is what worked for me: I'm only sharing this because I couldn't get either of his solutions to work on my rig. To see the currently active version, type nvm list.Type nvm install 6.10.2 (to install node version 6.10.2).Open your favourite console (CMD, Cmder, PowerShell).Once you have nvm, installing any node version is super easy: = EDIT: Better way to install node and npmĪs of today (), the best way to install and manage node and npm is to install nvm (Node Version Manager) as explained here.
This was npm version 1.4.9 and wouldn't update no matter what one did including uninstall and reinstall NodeJs. I had (age ago) installed npm via chocolatey, which created a chocolatey initiated npm.exe in C:\ProgramData\chocolatey\bin\npm.exe.
0 kommentar(er)
