


Some strange issues can be resolved by simply running npm cache clean and trying again.Windows: If you're on Windows and you have a broken installation, the easiest thing to do is to reinstall node from the official installer (see this note about installing the latest stable version).npm not running the latest version on a Windows machine.npm hangs on Windows at addRemoteTarball.cb() never called! when using shrinkwrapped dependencies.Many ENOENT / ENOTEMPTY errors in output.npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxies.Running a Vagrant box on Windows fails due to path length issues.Error: ENOENT, stat 'C:\Users\\AppData\Roaming\npm' on Windows 7.
