unstale

npm / @noble/hashes

@noble/hashes

What changed in @noble/hashes 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

3 breaking4 security9 performance5 behavior and defaults9 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli on npm

@noble/hashes 230 changes

Breaking changes 3

Security 4

  • Use rejection cleanup to wipe work state if scheduling is aborted.

    2.4.0release notes

  • Passed options are protected against mutation and pollution.

    2.4.0release notes

  • Rejects output sizes that caused the engine to crash.

    2.4.0release notes

  • Improves zeroization.

    2.4.0release notes

Performance 9

Behavior and default changes 5

  • Cost options are optional, with defaults t: 3, m: 1024 ** 2 KiB, p: 1, and dkLen: 32; calls using more memory must set maxmem explicitly, whose default limit is 1 GiB.

    2.4.0release notes

  • Yields through scheduler.yield() when available or setTimeout otherwise, allowing timers, I/O, and rendering to progress; accepts optional rejection cleanup.

    2.4.0release notes

  • Yields through scheduler.yield() when available or setTimeout otherwise, allowing timers, I/O, and rendering to progress; accepts optional rejection cleanup.

    2.4.0release notes

  • Corrects the default maxmem to work with N: 2 ** 20, r: 8, and p: 1.

    2.4.0release notes

  • Error messages are improved and type checks are stricter throughout the library.

    2.3.0release notes

Fixes and other changes 9