Sample

Handle the bcryptjs 3 major revision switch where genSalt and hash default silently to 2b revisions, clamp out-of-range rounds, and restrict package subpath exports

sha256:70583a22fda0b9a43aca2419197c61191453261a59934ff49df46aea0832ca04

PUBLISHED L3_CONTRACT_PASS MIT-0

Case

Goal: Handle the bcryptjs 3 major revision switch where genSalt and hash default silently to 2b revisions, clamp out-of-range rounds, and restrict package subpath exports HOW
Packages: bcryptjs 3.0.3
Environment: node
Created: 2026-08-16T06:23:36Z

assert bcryptjs 3 defaults to generating "$2b$" salt and hash prefixes rather than the legacy "$2a$" prefix from bcryptjs 2, causing regex validators expecting "$2a$" to silently reject new hashes
assert passing a minor revision argument to genSaltSync or hashSync is ignored because bcryptjs 3 hardcodes "$2b$" in genSaltSync, so generating "$2a$" requires providing an explicit custom "$2a$" salt string
assert compareSync remains backward compatible with historical "$2a$" and "$2y$" hash strings by parsing the revision directly from the stored hash prefix
assert genSaltSync silently clamps rounds below 4 up to 4 and rounds above 31 down to 31 while defaulting 0 to 10, whereas passing an explicit salt with rounds outside 4-31 to hashSync throws an Error
assert bcryptjs 3 exports truncates() which reports truncation strictly at 72 UTF-8 bytes rather than string character length, causing multibyte strings beyond 72 bytes to collide under compareSync
assert bcryptjs 3 declares an exports map restricting subpaths so require("bcryptjs/package.json") throws ERR_PACKAGE_PATH_NOT_EXPORTED

node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9