Sample
Prevent Luxon ESM imports from breaking after a patch release
sha256:6c12ec9c508cd79b6da35f22471840c1ca3aebeecdcc564bbcdd7f28bc67edbc
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prevent Luxon ESM imports from breaking after a patch release HOW
- Packages
- luxon 3.7.2
- Environment
- node
- Created
- 2026-08-16T18:35:41Z
Commonly assumed
A correct `luxon` package with an ESM entry point allows `import { DateTime } from "luxon"` to execute normally from ES module code.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Importing `luxon` through a named ESM import from `node_modules` returns a usable `DateTime` export.
- `DateTime.fromISO("2025-07-09T00:00:00.000Z").toISO()` returns exactly `2025-07-09T00:00:00.000Z`.
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