grunt with new npm:install has problems on Windows

[Narretz]

The new npm install / caching behavior in grunt is causing some issues. Basically, when the new npm-install scripts tries to remove the contents of the node_modules folder I am getting a whole lot of cannot remove : File or Path name too long.
This is the stupid Windows restriction on very long file paths, I think.
Because of this, the following npm install + shrinkwrap copy is never called, so I am ending up with a half empty node_modules folder.
I can empty the node_modules folder manually and call scripts/npm/install-dependencies.sh directly and this works, but I'd be running into this problem every time the shrinkwrap changes.
Is it possible to delete the contents of node_modules differently?

cc @IgorMinar

[IgorMinar]

if rm fails, we don't want to try to install because npm will almost certainly not install all the files. so you'll see random errors at runtime.

can you figure out what needs to be done on windows to make the rm command just work?

I don't have easy access to windows nor the required expertise 😞

[Narretz]

It seems we can't use the rm command because Windows has a stupid 260 char restriction on file paths. It's a wontfix on joyents's side: nodejs/node-v0.x-archive#6960
There exists a module that emulates rm -rf specifically for node: https://github.com/isaacs/rimraf but I am not sure what would happen if it removes itself.
Or could we use npm uninstall x for all registered modules? I just checked, this works perfectly
That is, we'd need to get a list of modules in the package.json and then uninstall each of them manually

[IgorMinar]

try rimraf. measure if it adds significant overhead. if it does use it only on windows.

npm uninstall sounds very unefficient, but I don't know if it actually is.