Vigia

Upgrading nanoid from 5.x to 6.x

Comparison of the public API of nanoid 5.1.16 and 6.0.1, 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 signatures1
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports0

Removed exports

None detected.

Changed signatures

exportBeforeAfter
nanoid · customRandom<Type extends string>(alphabet: string, size: number, random: (bytes: number) => Uint8Array<ArrayBufferLike>): (size?: number | undefined) => Type<Type extends string>(alphabet: string, defaultSize: number, random: (bytes: number) => Uint8Array<ArrayBufferLike>): (size?: number | undefined) => Type

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node^18 || >=20^22 || ^24 || >=26

Frequently asked questions

What are the breaking changes when upgrading nanoid from 5 to 6?

Between nanoid 5.1.16 and 6.0.1, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in nanoid 6?

0 exports or members are newly marked as deprecated in nanoid 6.0.1.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/nanoid/upgrade?from=5.1.16&to=6.0.1