Rimraf is a Node.js cross-platform implementation of the UNIX `rm -rf` command, for aggressively and recursively deleting files and directories. It provides async and synchronous APIs, supports options like path filtering and abort signals, and includes platform-specific strategies (including Windows handling).
Project status
- The
isaacs/rimrafrepo appears to be in active maintenance, with a recent upstream push on 2026-05-15, and priorupdatescontinuing through 2026 (v6.1.3 on 2026-02-16). - Apparent cadence is low-to-moderate, with
updatesspaced months apart (v6.1.3 on 2026-02-16, v6.1.2 and v6.1.1 both on 2025-11-19), and no new taggedupdatesshown after v6.1.3 up to today (2026-08-12).
AI summary generated
Recent updates
v6.1.3
v6.1.3 was published with release notes that did not include any documented changes. The diff shows mostly formatting-only edits, plus some significant non-code repository changes and dependency bumps (not described anywhere in the release notes).
v6.1.2
Release v6.1.2 contains no provided release notes. The code diff shows a version bump plus an upgrade of rimraf's direct dependency on glob, with corresponding lockfile updates.
v6.1.1
Release v6.1.1 was published on 2025-11-19, but the publisher provided no release notes (no changes described). Without documented notes, there is no actionable information available about features, fixes, breaking changes, or migrations in this release.
v6.1.0
No publisher release notes were provided for v6.1.0, so there is nothing documented to validate against. The code diff shows a broad internal refactor, plus CLI and build configuration changes that may affect runtime compatibility and developer expectations.
v5.0.10
Release v5.0.10 has no published release notes. The code diff shows only package metadata changes: the version is bumped from 5.0.9 to 5.0.10, npm publish configuration is adjusted, and the package.json engines field is removed.
Breakingv6.0.1
No release notes content was provided for v6.0.1. The code changes for this release are centered on adding a new CLI option, --version, and exposing the version value from the CLI entrypoint. The implementation also switches how package.json version is loaded and adds corresponding tests and documentation updates.
Featuresv6.0.0
This v6.0.0 release updates the package metadata, build configuration, and dependency set compared to v5.0.9. The provided release notes are empty, so the main changes must be inferred from the code diff, which includes a Node engine support drop and multiple dependency and build toolchain adjustments.
v5.0.9
Release v5.0.9 contains no publisher-provided release notes. The code diff shows only version metadata updates plus a change to the declared Node.js engine compatibility range in package.json, with no changes to runtime logic.
v5.0.8
Release v5.0.8 contains no publisher-provided release notes. The diff shows mostly metadata and tooling changes, plus a notable runtime environment requirement change via the package engines field.
Breakingv5.0.7
Release v5.0.7 was published on 2024-05-12, but no release notes were provided by the publisher. As a result, the changes included in this version are not described, so developers should review the diff and changelog history before upgrading.