Commit fcbdb06
fs: remove experimental from rmdir recursive
Refs: #34278
PR-URL: #35171
Reviewed-By: Christopher Hiller <boneskull@boneskull.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>1 parent 862b75d commit fcbdb06
1 file changed
Lines changed: 18 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3502,8 +3502,6 @@ changes: | |||
| 3502 | 3502 | it will emit a deprecation warning with id DEP0013. | |
| 3503 | 3503 | --> | |
| 3504 | 3504 | ||
| 3505 | - > Stability: 1 - Recursive removal is experimental. | ||
| 3506 | - | ||
| 3507 | 3505 | * `path` {string|Buffer|URL} | |
| 3508 | 3506 | * `options` {Object} | |
| 3509 | 3507 | * `maxRetries` {integer} If an `EBUSY`, `EMFILE`, `ENFILE`, `ENOTEMPTY`, or | |
@@ -3526,6 +3524,12 @@ to the completion callback. | |||
| 3526 | 3524 | Using `fs.rmdir()` on a file (not a directory) results in an `ENOENT` error on | |
| 3527 | 3525 | Windows and an `ENOTDIR` error on POSIX. | |
| 3528 | 3526 | ||
| 3527 | + Setting `recursive` to `true` results in behavior similar to the Unix command | ||
| 3528 | + `rm -rf`: an error will not be raised for paths that do not exist, and paths | ||
| 3529 | + that represent files will be deleted. The permissive behavior of the | ||
| 3530 | + `recursive` option is deprecated, `ENOTDIR` and `ENOENT` will be thrown in | ||
| 3531 | + the future. | ||
| 3532 | + | ||
| 3529 | 3533 | ## `fs.rmdirSync(path[, options])` | |
| 3530 | 3534 | <!-- YAML | |
| 3531 | 3535 | added: v0.1.21 | |
@@ -3549,8 +3553,6 @@ changes: | |||
| 3549 | 3553 | `file:` protocol. Support is currently still *experimental*. | |
| 3550 | 3554 | --> | |
| 3551 | 3555 | ||
| 3552 | - > Stability: 1 - Recursive removal is experimental. | ||
| 3553 | - | ||
| 3554 | 3556 | * `path` {string|Buffer|URL} | |
| 3555 | 3557 | * `options` {Object} | |
| 3556 | 3558 | * `maxRetries` {integer} If an `EBUSY`, `EMFILE`, `ENFILE`, `ENOTEMPTY`, or | |
@@ -3570,6 +3572,12 @@ Synchronous rmdir(2). Returns `undefined`. | |||
| 3570 | 3572 | Using `fs.rmdirSync()` on a file (not a directory) results in an `ENOENT` error | |
| 3571 | 3573 | on Windows and an `ENOTDIR` error on POSIX. | |
| 3572 | 3574 | ||
| 3575 | + Setting `recursive` to `true` results in behavior similar to the Unix command | ||
| 3576 | + `rm -rf`: an error will not be raised for paths that do not exist, and paths | ||
| 3577 | + that represent files will be deleted. The permissive behavior of the | ||
| 3578 | + `recursive` option is deprecated, `ENOTDIR` and `ENOENT` will be thrown in | ||
| 3579 | + the future. | ||
| 3580 | + | ||
| 3573 | 3581 | ## `fs.stat(path[, options], callback)` | |
| 3574 | 3582 | <!-- YAML | |
| 3575 | 3583 | added: v0.0.2 | |
@@ -5451,6 +5459,12 @@ Using `fsPromises.rmdir()` on a file (not a directory) results in the | |||
| 5451 | 5459 | `Promise` being rejected with an `ENOENT` error on Windows and an `ENOTDIR` | |
| 5452 | 5460 | error on POSIX. | |
| 5453 | 5461 | ||
| 5462 | + Setting `recursive` to `true` results in behavior similar to the Unix command | ||
| 5463 | + `rm -rf`: an error will not be raised for paths that do not exist, and paths | ||
| 5464 | + that represent files will be deleted. The permissive behavior of the | ||
| 5465 | + `recursive` option is deprecated, `ENOTDIR` and `ENOENT` will be thrown in | ||
| 5466 | + the future. | ||
| 5467 | + | ||
| 5454 | 5468 | ### `fsPromises.stat(path[, options])` | |
| 5455 | 5469 | <!-- YAML | |
| 5456 | 5470 | added: v10.0.0 | |
0 commit comments