rimraf - npm Package Compare versions
Comparing version 5.0.7 to 5.0.8
| { | ||
| "name": "rimraf", | ||
| "version": "5.0.7", | ||
| "version": "5.0.8", | ||
| "type": "module", | ||
@@ -64,3 +64,3 @@ "tshy": { | ||
| "prettier": "^3.2.5", | ||
| "tap": "^18.5.4", | ||
| "tap": "^19.0.1", | ||
| "tshy": "^1.14.0", | ||
@@ -74,3 +74,3 @@ "typedoc": "^0.25.13", | ||
| "engines": { | ||
| "node": ">=14.18" | ||
| "node": ">=18" | ||
| }, | ||
@@ -77,0 +77,0 @@ "dependencies": { |
@@ -11,3 +11,3 @@ The [UNIX command](<http://en.wikipedia.org/wiki/Rm_(Unix)>) `rm -rf` for node | ||
| - There is no default export anymore. Import the functions directly | ||
| using, e.g., `import { rimrafSync } from 'rimraf`. | ||
| using, e.g., `import { rimrafSync } from 'rimraf'`. | ||
@@ -25,5 +25,5 @@ ### v3 to v4 | ||
| resolve the situation. | ||
| - Simplified implementation on Posix, since the Windows | ||
| - Simplified implementation on POSIX, since the Windows | ||
| affordances are not necessary there. | ||
| - As of 4.3, return/resolve value is boolean instead of undefined | ||
| - As of 4.3, return/resolve value is boolean instead of undefined. | ||
@@ -58,3 +58,3 @@ ## API | ||
| not allowed. | ||
| - `tmp`: Windows only. Temp folder to use to place files and | ||
| - `tmp`: Windows only. Temp folder to place files and | ||
| folders for the "move then remove" fallback. Must be on the | ||
@@ -81,3 +81,3 @@ same physical device as the path being deleted. Defaults to | ||
| removal. This is useful when removing large folder structures, | ||
| if you'd like to limit the amount of time spent. | ||
| if you'd like to limit the time spent. | ||
@@ -91,3 +91,3 @@ Using a `signal` option prevents the use of Node's built-in | ||
| - `filter` Method that returns a boolean indicating whether that | ||
| path should be deleted. With async rimraf methods, this may | ||
| path should be deleted. With async `rimraf` methods, this may | ||
| return a Promise that resolves to a boolean. (Since Promises | ||
@@ -106,3 +106,3 @@ are truthy, returning a Promise from a sync filter is the same | ||
| they are also filtered out, but any parents of a filtered entry | ||
| will not be removed, since the directory would not be empty in | ||
| will not be removed, since the directory will not be empty in | ||
| that case. | ||
@@ -116,3 +116,3 @@ | ||
| This will attempt to choose the best implementation, based on Node.js | ||
| This will attempt to choose the best implementation, based on the Node.js | ||
| version and `process.platform`. To force a specific implementation, use | ||
@@ -171,3 +171,3 @@ one of the other functions provided. | ||
| provides a way to perform atomic `unlink` and `rmdir` operations, | ||
| this is unfortunately unavoidable. | ||
| this is, unfortunately, unavoidable. | ||
@@ -174,0 +174,0 @@ To move files to a different temporary directory other than the |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Worsened metrics
- Total package byte prevSize
281205