chore(deps): bump nanoid from 3.3.11 to 3.3.16

[dependabot]

Bumps nanoid from 3.3.11 to 3.3.16.

Release notes

Sourced from nanoid's releases.

3.3.16

• Fixed infinite loop on negative size (by @​greymoth-jp).

3.3.15

• Fixed npm provenance error.

3.3.14

• Fixed random pool corruption on big ID sizes.

3.3.13

• Reduced npm package size.

3.3.12

• Fixed breaking Nano ID by requesting big ID.

Changelog

Sourced from nanoid's changelog.

3.3.16

• Fixed infinite loop on negative size (by @​greymoth-jp).

3.3.15

• Fixed npm provenance error.

3.3.14

• Fixed random pool corruption on big ID sizes.

3.3.13

• Reduced npm package size.

3.3.12

• Fixed breaking Nano ID by requesting big ID.

Commits

• 9760e11 Release 3.3.16 version
• e835c9b fix(non-secure): clamp negative size to prevent infinite loop (#601)
• 96dd086 Update CI action
• ba0bc3b Do not create latest release for v3
• 6819724 Release 3.3.15 version
• fb0b137 Fix tag for v3
• e084bc9 Back-port new release system and fix pre-commit hook
• 7e32945 Release 3.3.14 version
• 6bd27b8 Another way to deal with pool damage
• 41ad2ac Reduce ID size
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for nanoid since your current version.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[AminDhouib]

Diagnosis: this lockfile regen floats @types/node, whose newer types make Buffer<ArrayBufferLike> unassignable to BodyInit — the board-wide red is real, not flake. #353 fixes the first breakage (@upupjs/next pages-handler, now typed RequestInit['body'] and verified against both old and new @types/node). Known residue this branch will still hit after a rebase: @upupjs/core + @upupjs/storybook-config test fixtures (Uint8Array<ArrayBufferLike> vs BlobPart) and apps/next-example (TS2305). Plan: once #353 reaches master, rebase this PR and fix the remaining fixture typings.