Temporal API Migration Workbench: Replace Legacy JavaScript Dates

Live Production Scenario: Flight Booking & DST Jump

Test the notorious Sydney (UTC+11) flight booking stored into a UTC Node.js database across Daylight Saving Time boundaries.

Booking Date (Local)

Booking Time (Local)

Origin Timezone (IANA)

Server Database Target

Arithmetic: Days to Add

Legacy Date (1995-2026) Mutable & Flawed

Off-by-one / DST Hazards

Executed JavaScript Snippet

const d = new Date(2026, 10, 3);
d.setDate(d.getDate() + 1);

Constructed Month: new Date(2026, 10, 3) → November (Month 11)

Immutability Test: MUTATED (Original instance corrupted)

Database Storage State: Node.js UTC ISO String

Resulting Computed Output

2026-11-04T03:00:00.000Z (UTC storage shift bug)

🚨 Timezone Shift Bug: Flight local departure is 14:00 AEDT, but serializing to UTC stores 03:00:00.000Z. When viewed on different server timezones, the flight day shifts backwards, and `setDate` mutates the original reference without preserving original IANA timezone rules.

ES2026 Temporal API 100% Immutable

Native IANA Timezone Engine

ES2026 Refactored Code

const zdt = Temporal.ZonedDateTime.from('2026-11-03T14:00:00+11:00[Australia/Sydney]');
const futureZdt = zdt.add({ days: 1 });

1-Based Month: Month 11 === November (0-index eliminated)

Immutability Test: PASS (Original instance frozen)

DST Boundary Guard: Preserves wall-clock 14:00 AEDT

Resulting Computed Output

2026-11-04T14:00:00+11:00 [Australia/Sydney]

✅ Accurate Timezone Arithmetic: Temporal.ZonedDateTime retains timezone offset, DST rules, and exact local wall-clock time across additions. Database migrations serialize safely using ISO 8601 with IANA annotations.

Automated Temporal Refactoring Engine

Select an existing legacy Date, date-fns, or Moment.js pattern to generate the modern ES2026 Temporal replacement:

Legacy Pattern

// date-fns or native Date
const start = new Date(2026, 10, 3, 14, 0);
start.setDate(start.getDate() + 1); // Mutates!

Native ES2026 Temporal Replacement

const zdt = Temporal.ZonedDateTime.from('2026-11-03T14:00:00+11:00[Australia/Sydney]');
const futureZdt = zdt.add({ days: 1 });

Architectural Comparison: Legacy Date vs ES2026 Temporal

Capability	Legacy JavaScript Date	ES2026 Temporal API	Production Impact
State Mutability	Mutable (calls to setDate alter original)	100% Immutable (returns new instances)	Prevents shared state bugs across components
Month Indexing	0-Indexed (0 = January, 10 = November)	1-Indexed (1 = January, 11 = November)	Eliminates off-by-one calendar & booking mistakes
Daylight Saving Time (DST)	Implicit local host bias, 23/25 hour drift	Explicit calendar day arithmetic in IANA zone	Flights & hotel stays preserve true wall-clock time
Date Without Time	None (forced epoch milliseconds)	`Temporal.PlainDate`	Clean birthdays, anniversaries, and expiry dates
Dependencies	Requires Moment.js, date-fns, or Luxon	Zero npm packages required	Shrinks frontend bundles by 50KB-120KB