rimraf breaking changes
Every breaking API change we have recorded in rimraf on npm: 26 breaking changes in 2 versions. Below are its newest 2 versions, removals and renames first, each with its source.
Newest change March 4, 2023

On this page
4.3.0
- Removed
RimrafOptions.backoff
RimrafOptions.backoff was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.glob
RimrafOptions.glob was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.maxBackoff
RimrafOptions.maxBackoff was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.maxRetries
RimrafOptions.maxRetries was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.preserveRoot
RimrafOptions.preserveRoot was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.retryDelay
RimrafOptions.retryDelay was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.signal
RimrafOptions.signal was removed in rimraf 4.3.0 npmjs.com - Removed
RimrafOptions.tmp
RimrafOptions.tmp was removed in rimraf 4.3.0 npmjs.com - Signature changed
default
Was const rimraf: ((path: string | string[], opt?: RimrafOptions) => Promise<void>) & {rimraf: ((path: string | string[], opt?: RimrafOptions) => Promise<void>) & {sync: (path: string | string[], opt?: RimrafOptions) => void;}; sync... npmjs.com - Signature changed
manual
Was const manual: ((path: string | string[], opt?: RimrafOptions) => Promise<void>) & {sync: (path: string | string[], opt?: RimrafOptions) => void;}; now const manual: ((path: string | string[], opt?: RimrafAsyncOptions) =>... npmjs.com
And 13 more in this version.
4.0.0
- Removed
Options
Options was removed in rimraf 4.0.0 npmjs.com - Signature changed
default
Was function rimraf(path: string, callback: (error: Error | null | undefined) => void): void function rimraf(path: string, options: rimraf.Options, callback: (error: Error | null | undefined) => void): void namespace rimraf; now const... npmjs.com - Signature changed
sync
Was function sync(path: string, options?: Options): void; now const sync: (path: string | string[], opt?: RimrafOptions) => void. npmjs.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.

Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp