This creates a mess as all modules go into %appdata%, and when you upgrade NPM itself - which NPM themselves recommend you do right away - you end up with two copies: the original still in 'program files' since NPM can't erase that, and the new one inn %appdata%.Įven worse, if you mistakenly perform NPM operations as admin (much easier on Windows then on *nix) then it will operate on the 'program files' copy of NPM node_modules. The default MSI installer puts Node and the NPM that comes with it in 'program files' and adds this to the system path, but it sets the user path for NPM to %appdata% (c:\users\appdata\roaming) since the user doesn't have sufficient priveleges to write to 'program files'. Re-start the command prompt and npm will now work.Įverything should be installed in %appdata% (C:\Users\\AppData\Roaming), not 'program files'. Manually go into the AppData directory and you will find that there is no npm directory inside Roaming.
Now that the PATH variable is set correctly, you will still encounter errors. If the PATH variable is empty, change it to this: C:\Users\\AppData\Roaming\npm C:\Program Files\nodejs
How to install nodejs windows 10 64 bits#
download the 64 bits version, 32 is for hipsters.To install the Node.js extension pack: Open the Extensions window (Ctrl+Shift+X) in VS Code. Install them all or pick and choose which seem the most useful to you. It seems like new installers do not have this problem anymore, see this answer by Parag Meshram as my answer is likely obsolete now. We recommend you install Visual Studio Code, as well as the Node.js Extension Pack, for developing with Node.js on Windows.
0 kommentar(er)
