rimraf doesn't work to remove grunt-contrib-imagemin

[emalherbi-zz]

Hi.

CMD:

PowerShell:

[nicothin]

+1.
error log:

rimraf D:\projects\HTMLACADEMY_advanced-intensive\barbershop\node_modules
C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:302
throw er
^
Error: ENOTEMPTY, directory not empty 'D:\projects\HTMLACADEMY_advanced-intensive\barbershop\node_modules\grunt-contrib-imagemin\node_modules\imagemin\node_modules\imagemin-gifsicle\node_modules\gifsicle\node_modules\bin-wrapper\node_modules\download\node_modules\vinyl-fs\node_modules\glob-watcher\node_modules\gaze\node_modules\globule\node_modules\minimatch'
at Error (native)
at Object.fs.rmdirSync (fs.js:715:18)
at rmkidsSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:332:11)
at rmdirSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:322:7)
at rimrafSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:293:9)
at C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:330:5
at Array.forEach (native)
at rmkidsSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:329:26)
at rmdirSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:322:7)
at rimrafSync (C:\Users\nicothin\AppData\Roaming\npm\node_modules\rimraf\rimraf.js:293:9)

win 7 64

[Ernesto-Valdes]

+1

same error on multiple instances for the same grunt-contrib-imagemin node module.

win 7 64

[jorrit]

The problem is that the retry mechanisms that should handle this problem is not implemented in the sync version of the command. When starting a REPL node session and invoking rimraf the folder is deleted.

[edit]
I was reading the npm@3 release notes and it seems the deeply nested modules problem is addressed in that version. See https://github.com/npm/npm/releases/tag/v3.0.0

[isaacs]

Yeah, you can't very well retry a sync operation after a bit of a wait.

Perhaps the rimraf binary should be using the async function instead?

[vpraveen]

I had the same problem, but it got fixed as soon as I closed one instance of git bash. Both instances were opened in the same folder.