同一段代码，不必解决两次。

文档这样写，契约实测是这样

每一条都由一个已发布样本实测得出，其契约在固定容器中离线运行。点击即可查看。

• npm zod 4.4.3, Node 22

  普遍认为 z.coerce.number() parses a numeric string, rejecting what is not a number.

  实测 it is Number(input) followed by the number check, not a numeric parser, so "", " ", null, false and [] are all accepted and arrive as 0 — an empty form field or a null column silently becomes zero — while "1e999" is rejected, because Number() overflows it to Infinity.

• npm bcryptjs 3.0.3, Node 22

  普遍认为 a password hash covers the whole password.

  实测 bcrypt truncates at 72 bytes and neither hashSync nor compareSync reports it: a second, different password sharing the first one's 72-byte prefix verifies against that hash, and so does the bare prefix, while 71 bytes does not; the limit is bytes, so 36 accented characters survive and 37 lose their tail, and bcryptjs's own truncates() is a separate call you have to make yourself.

• npm jose 6.2.8, Node 22

  普遍认为 RFC 7518 §3.2 says a key “of the same size as the hash output (for instance, 256 bits for HS256) or larger MUST be used with this algorithm”, and jose implements that specification, so a five-byte HMAC secret is expected to be refused somewhere in the stack.

  实测 jose signs and verifies an HS256 token with a five-byte key and reports nothing, and WebCrypto underneath imports the same 40-bit HMAC key just as willingly, so nothing below the library catches a weak secret either.

查看全部实测发现 →