Vigia

Upgrading uuid from 13.x to 14.x

Comparison of the public API of uuid 13.0.2 and 14.0.2, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures2
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)0
New exports1

Removed exports

None detected.

Changed signatures

exportBeforeAfter
uuid · parse(uuid: string): Uint8Array<ArrayBufferLike>(uuid: string): Uint8Array<ArrayBuffer>
uuid · v1ToV6(uuid: string): string | (uuid: Uint8Array<ArrayBufferLike>): Uint8Array<ArrayBufferLike>(uuid: string): string | (uuid: Uint8Array<ArrayBufferLike>): Uint8Array<ArrayBuffer>

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

None detected.

New exports (1)
importexportkind
uuidNonSharedArrayBuffertype

Frequently asked questions

What are the breaking changes when upgrading uuid from 13 to 14?

Between uuid 13.0.2 and 14.0.2, Vigia found 0 removed exports, 2 changed signatures and 0 removed or changed class or interface members.

What became deprecated in uuid 14?

0 exports or members are newly marked as deprecated in uuid 14.0.2.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/uuid/upgrade?from=13.0.2&to=14.0.2