nanoid breaking changes
Every breaking API change we have recorded in nanoid on npm: 3 breaking changes in 2 versions. Below are its newest 2 versions, removals and renames first, each with its source.
Newest change July 12, 2026
On this page
6.0.0
- Removed
The package no longer supports Node.js 18 and 20. Users on those Node.js versions must upgrade Node.js before upgrading to this release. github.com - Signature changed
customRandom
Was function customRandom<Type extends string>(alphabet: string, size: number, random: (bytes: number) => Uint8Array): (size?: number) => Type; now function customRandom<Type extends string>(alphabet: string, defaultSize: number, random... npmjs.com
5.1.7
- Signature changed
customRandom
Was function customRandom<Type extends string>(alphabet: string, size: number, random: (bytes: number) => Uint8Array): () => Type; now function customRandom<Type extends string>(alphabet: string, size: number, random: (bytes: number) =>... npmjs.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp