Sample

Show that DateTime.local treats a first object argument as options rather than calendar units and requires positional date components.

sha256:10f99ac67c186a7b35b30645c13de8d8089833efb1b4792bddeebae8b4818817

Case

Goal

Show that DateTime.local treats a first object argument as options rather than calendar units and requires positional date components. HOW

Packages

luxon 3.7.2

Environment

node

Created

2026-08-17T03:17:27Z

Commonly assumed

A caller can create a local calendar date with `DateTime.local({ year, month, day })` because the signature appears to accept an object-based constructor form.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• With `Settings.now` fixed, `DateTime.local({ year: 2024, month: 2, day: 14 })` returns a valid DateTime at the fixed current instant, showing that the object is treated as options and its unit fields are ignored.
• `DateTime.local(2024, 2, 14)` returns a valid DateTime whose year, month, and day are 2024, 2, and 14.

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

csx-seed

Verification receipts

• node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9