Upgrading diff from 8.x to 9.x
Comparison of the public API of diff 8.0.4 and 9.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 | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 4 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
StructuredPatch.newFileName | string | string | undefined |
StructuredPatch.oldFileName | string | string | undefined |
StructuredPatch.newFileName | string | string | undefined |
StructuredPatch.oldFileName | string | string | undefined |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Frequently asked questions
What are the breaking changes when upgrading diff from 8 to 9?
Between diff 8.0.4 and 9.0.0, Vigia found 0 removed exports, 0 changed signatures and 4 removed or changed class or interface members.
What became deprecated in diff 9?
0 exports or members are newly marked as deprecated in diff 9.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/diff/upgrade?from=8.0.4&to=9.0.0