Upgrading schema-utils from 3.x to 4.x
Comparison of the public API of schema-utils 3.3.0 and 4.5.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 | 1 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 6 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
ValidationError.formatSchema | (schema: any, logic?: boolean | undefined, prevSchemas?: Object[] | undefined): string | (schema: any, logic?: boolean | undefined, prevSchemas?: object[] | undefined): string |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
New exports (6)
| import | export | kind |
|---|---|---|
schema-utils | Schema | type |
schema-utils | JSONSchema4 | type |
schema-utils | JSONSchema6 | type |
schema-utils | JSONSchema7 | type |
schema-utils | ExtendedSchema | type |
schema-utils | ValidationErrorConfiguration | type |
Frequently asked questions
What are the breaking changes when upgrading schema-utils from 3 to 4?
Between schema-utils 3.3.0 and 4.5.0, Vigia found 0 removed exports, 0 changed signatures and 1 removed or changed class or interface members.
What became deprecated in schema-utils 4?
0 exports or members are newly marked as deprecated in schema-utils 4.5.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/schema-utils/upgrade?from=3.3.0&to=4.5.0