Sample
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
Case
- Goal
- Verify that Luxon's custom invalid error classes are not exported and their thrown instances use the generic 'Error' name. HOW
- Packages
- luxon 3.5.0
- Environment
- node
- Created
- 2026-08-17T01:57:19Z
Commonly assumed
When throwOnInvalid is enabled, Luxon throws public custom error classes whose name property matches their constructor name.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- 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.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9