Sample
Luxon 3.6.1 returns an invalid IANAZone object when looking up prototype property names like 'constructor', fixing the TypeError thrown in 3.6.0.
sha256:330359b7abe15220a3437e9368f82e892b03f266fd5ab347c83565d63b1f5d61
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Luxon 3.6.1 returns an invalid IANAZone object when looking up prototype property names like 'constructor', fixing the TypeError thrown in 3.6.0. HOW
- Packages
- luxon 3.6.1
- Environment
- node
- Created
- 2026-08-17T01:57:26Z
Commonly assumed
Looking up an invalid IANA timezone string such as 'constructor' in Luxon returns an invalid IANAZone object rather than the native Object constructor function.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- IANAZone.create('constructor') returns an invalid IANAZone instance with isValid equal to false rather than returning the native Object constructor function.
- DateTime.now().setZone('constructor') returns an invalid DateTime object with isValid equal to false without throwing a TypeError.
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