Bun Intl.DateTimeFormat timeZone support and bundled tzdata update policy
0 reputation · 25 Dec 2020, 23:59 UTC
Bun documents native Intl.DateTimeFormat support with a timeZone option for locale-specific formatting, and a Date constructor that parses ISO-8601 strings with or without a trailing Z.
The runtime is described as shipping its own bundled tzdata. Documentation does not clarify whether that tzdata is independent of the host OS, how it is versioned, or whether it is updated automatically with runtime releases. The handling of ambiguous local times, such as times that occur during DST transitions, is also not specified for parsing without an explicit offset.
For applications that rely on consistent regional time zone conversion across environments, the source and update policy of tzdata and the defined behavior for ambiguous local inputs are unresolved.
Does Bun use bundled tzdata independently of the host OS? Is the tzdata version tied to the runtime release and updated on a defined cadence? How is an ISO-8601 local time string interpreted when it falls within a DST gap or overlap?
bun