Upgrading uri-js from 3.x to 4.x
Comparison of the public API of uri-js 3.0.2 and 4.4.1, 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 | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 2 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
uri-js · SCHEMES | { [scheme: string]: URISchemeHandler; } | { [scheme: string]: URISchemeHandler<URIComponents, URIOptions, URIComponents>; } |
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
URISchemeHandler.parse | (components: URIComponents, options: URIOptions): URIComponents | (components: ParentComponents, options: Options): Components |
URISchemeHandler.serialize | (components: URIComponents, options: URIOptions): URIComponents | (components: Components, options: Options): ParentComponents |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Frequently asked questions
What are the breaking changes when upgrading uri-js from 3 to 4?
Between uri-js 3.0.2 and 4.4.1, Vigia found 0 removed exports, 1 changed signatures and 2 removed or changed class or interface members.
What became deprecated in uri-js 4?
0 exports or members are newly marked as deprecated in uri-js 4.4.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/uri-js/upgrade?from=3.0.2&to=4.4.1