示例
Verify that Luxon's custom invalid error classes are not exported and their thrown instances use the generic 'Error' name.
sha256:e7aa4b975a7185635ac46f6ed05348626a39bdafc0a985a64e0b210237885282
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Verify that Luxon's custom invalid error classes are not exported and their thrown instances use the generic 'Error' name. HOW
- 包
- luxon 3.5.0
- 环境
- node
- 创建时间
- 2026-08-17T01:57:19Z
常见的想当然
When throwOnInvalid is enabled, Luxon throws public custom error classes whose name property matches their constructor name.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- Luxon's custom error classes (InvalidDateTimeError, InvalidDurationError, and InvalidIntervalError) are not exported, and their thrown instances have their name property set to 'Error' rather than their constructor names.
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9