If anEBUSY,ENOTEMPTY, orEPERMerror code is encountered on Windows systems, then rimraf will retry with a linear backoff wait of 100ms longer on each try. The default maxBusyTries is 3. Only relevant for async usage. emfileWait If anEMFILEerror is encountered, then rimraf will retry repeat...
Until the Windows kernel provides a way to perform atomic unlink and rmdir operations, this is unfortunately unavoidable. To move files to a different temporary directory other than the parent, provide opts.tmp. Note that this must be on the same physical device as the folder being deleted, ...
JavaScript implementation of file removal appropriate for Windows platforms. Works aroundunlinkandrmdirnot being atomic operations, andEPERMwhen deleting files with certain permission modes. First deletes all non-directory files within the tree, and then removes all directories, which should ideally be ...
In general the callback for each op should be called with cb(returnCode, [value]) where the return code is a number (0 for OK and < 0 for errors). See below for a list of POSIX error codes. ops.init(cb) Called on filesystem init. ops.access(path, mode, cb) Called before the...
If anEBUSY,ENOTEMPTY, orEPERMerror code is encountered on Windows systems, then rimraf will retry with a linear backoff wait of 100ms longer on each try. The default maxBusyTries is 3. Only relevant for async usage. emfileWait If anEMFILEerror is encountered, then rimraf will retry repeat...
If anEBUSY,ENOTEMPTY, orEPERMerror code is encountered on Windows systems, then rimraf will retry with a linear backoff wait of 100ms longer on each try. The default maxBusyTries is 3. Only relevant for async usage. emfileWait If anEMFILEerror is encountered, then rimraf will retry repeat...