Sample
In Luxon 3, specifying system as the zone always resolves to the host system zone and ignores Settings.defaultZone.
sha256:8d2b9cea97100faf30a7e95f31f32596bffe04c0d763bba5e9456ea2cd4918ab
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- In Luxon 3, specifying system as the zone always resolves to the host system zone and ignores Settings.defaultZone. HOW
- Packages
- luxon 3.5.0
- Environment
- node
- Created
- 2026-08-17T01:57:28Z
Commonly assumed
Setting Settings.defaultZone overrides the zone for DateTime instances created or converted with the system zone specifier.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- DateTime setZone('system') returns a SystemZone instance with type system rather than inheriting Settings.defaultZone.
- DateTime setZone('default') must be explicitly used to inherit the custom Settings.defaultZone.
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