Nvm-windows: Node.js Install (v4.2.4) does not properly install npm on Windows 10

[jennykwan]

As the title says.

I've tried changing the default %NVM_HOME% to C:\nvm\. I've also tried running nvm install 4.2.4 64 as Administrator. No dice.

Seems related to #62.

FWIW, node_modules/ is empty after Node.js installation. npm and npm.cmd are there, and both throw the missing npm_cli.js error.

[jennykwan]

Oh, this is not #75 because download is fine.

[coreybutler]

Which version are you running? Does nvm list show 4.2.4?

[tongzou]

I have the same problem. I installed node 5.4.1 and 0.12.9, both had empty node_modules. nvm list shows the correct version.

[jennykwan]

Yes, nvm list shows the correct version.

[sullivanpt]

Probably need a little more information to accurately diagnose the problem you are encountering. For reference, I am running nvm 1.1.0 on Windows 10 and am using it successfully to switch between node 5.4.0, 4.2.4, 4.1.0, 0.12.7, 0.10.4.

However, I have encountered at least one npm "segmentation fault" on 4.2.4 while running "npm install". In my case deleting the existing node_modules folder and running "npm cache clean; npm install" made the issue go away, but the unexplained seg. fault leaves a troubling bad taste.

My other suggestion from a previous anomaly (I weirdly triggered by reinstalling my git bash shell) is to completely uninstall all traces of nvm, then reinstall it using the installer's default options.

[jennykwan]

I'm using 1.10. node_modules/ is empty for the handful of Node.js versions I've tried. I can't even invoke npm from the command line without it raising the "can't find npm-cli.js" error. I've tried uninstalling cleanly and reinstalling several times.

I suspect an error being swallowed by the nvm install. Is there a debug flag? I'll try digging into the source code.

[coreybutler]

There is no debug flag, but there is a guide for hacking on NVM that might offer some value.

[santriseus]

I had similar issue, I was able to fix it when completely uninstall nvm, then choose the root directory paths like C:/nvm and C:/node during the installation. It looks for me it was the issue with the long system path.

[SebastianMetzger]

I use Windows 10 Pro and also stumbled on this empty "node_modules" folder issue where npm won't work.

The latest version that seems to work and correctly install npm is node v4.2.4
Maybe something changed after this release?

[deedaralam]

Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "gulp"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! path /lib
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access

npm ERR! Error: EACCES: permission denied, access '/lib'
npm ERR! at Error (native)
npm ERR! { Error: EACCES: permission denied, access '/lib'
npm ERR! at Error (native) errno: -13, code: 'EACCES', syscall: 'access', path: '/lib' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR! /Users/deedaralam/npm-debug.log

Please slove thiss issue kindly

[coreybutler]

@deedaralam - Darwin 16.0.0 indicates you're running this on a Mac. This is NVM for _Windows_.

Also, I think the solution is pretty straightforward where it says Please try running this command again as root/Administrator.