Due to its folder nesting Windows can't delete the folder as its name is too long. To solve this, install RimRaf:
npm install rimraf -g
and delete the node_modules folder easily with:
edit: If you happen to get an "error" like this:
C:\Users\Nikola\Desktop>npm install -g rimraf C:\Users\Nikola\AppData\Roaming\npm\rimraf -> C:\Users\Nikola\AppData\Roaming\npm\node_modules\rimraf\bin.js npm WARN unmet dependency C:\Users\Nikola\AppData\Roaming\npm\node_modules\generator-ionic requires [email protected]'^4.2.0' but will load npm WARN unmet dependency C:\Users\Nikola\AppData\Roaming\npm\node_modules\cordova, npm WARN unmet dependency which is version 5.1.1 npm WARN unmet dependency C:\Users\Nikola\AppData\Roaming\npm\node_modules\bower\node_modules\bower-registry-client requires [email protected]'~2.51.0' but will load npm WARN unmet dependency undefined, npm WARN unmet dependency which is version undefined npm WARN unmet dependency C:\Users\Nikola\AppData\Roaming\npm\node_modules\bower\node_modules\fstream-ignore requires [email protected]'^1.0.0' but will load npm WARN unmet dependency undefined, npm WARN unmet dependency which is version undefined npm ERR! peerinvalid The package node-inspector does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.7.0 npm ERR! System Windows_NT 6.1.7601 npm ERR! command "C:\\NodeJS\\\\node.exe" "C:\\NodeJS\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "rimraf" npm ERR! cwd C:\Users\Nikola\Desktop npm ERR! node -v v0.10.36 npm ERR! npm -v 1.4.28 npm ERR! code EPEERINVALID npm ERR! npm ERR! Additional logging details can be found in: npm ERR! C:\Users\Nikola\Desktop\npm-debug.log npm ERR! not ok code 0
Don't panic :), just try to run rimraf instead, as noted above. In most cases, all will be okay and you'll be able to use it without a problem. If not, head to the comments, and we'll take care of it together! For those who don't care much about comments, here's the post in which I address this node-inspector issue.
— Nikola Brežnjak (@HitmanHR) July 28, 2015