{"id":655,"date":"2014-08-22T09:41:45","date_gmt":"2014-08-22T09:41:45","guid":{"rendered":"http:\/\/www.nikola-breznjak.com\/blog\/?p=655"},"modified":"2015-09-08T09:04:21","modified_gmt":"2015-09-08T09:04:21","slug":"how-to-delete-node_modules-folder-on-windows-machine","status":"publish","type":"post","link":"https:\/\/nikola-breznjak.com\/blog\/javascript\/nodejs\/how-to-delete-node_modules-folder-on-windows-machine\/","title":{"rendered":"How to delete node_modules folder on Windows machine?"},"content":{"rendered":"

Due to its folder nesting<\/em> Windows can’t delete the folder as its name is too long. To solve this, install RimRaf<\/a>:<\/p>\n

npm install rimraf -g<\/pre>\n
and delete the node_modules folder easily with:<\/p>\n
rimraf node_modules<\/pre>\n
 <\/p>\n
edit:<\/strong>\u00a0If you happen to get an “error” like this:<\/p>\n
C:\\Users\\Nikola\\Desktop>npm install -g rimraf\r\nC:\\Users\\Nikola\\AppData\\Roaming\\npm\\rimraf -> C:\\Users\\Nikola\\AppData\\Roaming\\npm\\node_modules\\rimraf\\bin.js\r\nnpm WARN unmet dependency C:\\Users\\Nikola\\AppData\\Roaming\\npm\\node_modules\\generator-ionic requires cordova@'^4.2.0' but will load\r\nnpm WARN unmet dependency C:\\Users\\Nikola\\AppData\\Roaming\\npm\\node_modules\\cordova,\r\nnpm WARN unmet dependency which is version 5.1.1\r\nnpm WARN unmet dependency C:\\Users\\Nikola\\AppData\\Roaming\\npm\\node_modules\\bower\\node_modules\\bower-registry-client requires request@'~2.51.0' but will load\r\nnpm WARN unmet dependency undefined,\r\nnpm WARN unmet dependency which is version undefined\r\nnpm WARN unmet dependency C:\\Users\\Nikola\\AppData\\Roaming\\npm\\node_modules\\bower\\node_modules\\fstream-ignore requires fstream@'^1.0.0' but will load\r\nnpm WARN unmet dependency undefined,\r\nnpm WARN unmet dependency which is version undefined\r\nnpm ERR! peerinvalid The package node-inspector does not satisfy its siblings' peerDependencies requirements!\r\nnpm ERR! peerinvalid Peer strong-cli@2.6.4 wants node-inspector@~0.7.0\r\n\r\nnpm ERR! System Windows_NT 6.1.7601\r\nnpm ERR! command \"C:\\\\NodeJS\\\\\\\\node.exe\" \"C:\\\\NodeJS\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js\" \"install\" \"-g\" \"rimraf\"\r\nnpm ERR! cwd C:\\Users\\Nikola\\Desktop\r\nnpm ERR! node -v v0.10.36\r\nnpm ERR! npm -v 1.4.28\r\nnpm ERR! code EPEERINVALID\r\nnpm ERR!\r\nnpm ERR! Additional logging details can be found in:\r\nnpm ERR!     C:\\Users\\Nikola\\Desktop\\npm-debug.log\r\nnpm ERR! not ok code 0<\/pre>\n
Don’t panic :), just try to run rimraf<\/strong> 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<\/a>.<\/p>\n
\n
How to delete node_modules folder on Windows machine? http:\/\/t.co\/0pV4OSTG1L<\/a> #nodejs<\/a> #windows<\/a> #node_modules<\/a><\/p>\n
— Nikola Bre\u017enjak (@HitmanHR) July 28, 2015<\/a><\/p><\/blockquote>\n