Upgrading chokidar from 4.x to 5.x
Comparison of the public API of chokidar 4.0.3 and 5.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 1 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 1 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
chokidar | FSWatcherKnownEventMap | interface | interface |
Changed signatures
| export | Before | After |
|---|---|---|
chokidar · FSWatcherEventMap | FSWatcherKnownEventMap & { add: EmitArgs; change: EmitArgs; addDir: EmitArgs; unlink: EmitArgs; unlinkDir: EmitArgs; } | interface |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >= 14.16.0 | >= 20.19.0 |
New exports (1)
| import | export | kind |
|---|---|---|
chokidar | AWF | type |
Frequently asked questions
What are the breaking changes when upgrading chokidar from 4 to 5?
Between chokidar 4.0.3 and 5.0.0, Vigia found 1 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in chokidar 5?
0 exports or members are newly marked as deprecated in chokidar 5.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/chokidar/upgrade?from=4.0.3&to=5.0.0