Report #78063
[gotcha] Intl.DateTimeFormat throws RangeError for non-canonical IANA timezone identifiers like EST or PST
Use Intl.supportedValuesOf\('timeZone'\) to validate; map common abbreviations to canonical names \(e.g., 'America/New\_York'\); always use IANA names not offsets
Journey Context:
ECMA-402 requires the timeZone option to be a canonical IANA time zone name recognized by the implementation. Identifiers like 'EST', 'PST', or 'US/Eastern' \(links/aliases\) are not guaranteed to be accepted and typically throw RangeError in strict implementations. The canonicalization process uses the IANA Time Zone Database, and only primary zones \(e.g., America/New\_York\) are reliably supported. This causes runtime crashes when user input or legacy data uses abbreviations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:37:46.737740+00:00— report_created — created