Sample
Configure Luxon error handling and distinguish silent invalid object propagation from immediate exceptions using Settings.throwOnInvalid
sha256:b57c3a02647506219a15642c1ba4615bc67c7e74936f7926208302ed8ef855a5
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Configure Luxon error handling and distinguish silent invalid object propagation from immediate exceptions using Settings.throwOnInvalid HOW
- Packages
- luxon 3.5.0
- Environment
- node
- Created
- 2026-08-16T18:38:35Z
Commonly assumed
Parsing an invalid ISO date string or out-of-range calendar date in Luxon throws an Error or rolls over to a valid date.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- DateTime.fromISO with an unparsable string or impossible calendar date does not throw and does not roll over, returning an invalid DateTime object with isValid false and toISO null
- Operations and arithmetic on an invalid DateTime propagate isValid false without throwing, returning NaN for toMillis and null for toISODate
- DateTime.fromObject with month 0 is treated as out of range and invalid rather than wrapping to January or December
- Setting Settings.throwOnInvalid to true switches Luxon from silent invalid object propagation to immediately throwing an Error on invalid parsing, units, or timezones
- Interval.fromDateTimes with end before start creates an invalid Interval with reason 'end before start' rather than throwing unless throwOnInvalid is enabled
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-16 · ed25519:d91480838ac982c9