"Starting with Chrome 144, support for the Temporal API has been added, bringing a modern date and time API to the web and marking the first stable Chrome release to ship the long-running TC39 proposal. The change was highlighted in Chrome's release blog, which positions Temporal as a modern alternative to JavaScript's long criticised Date object. Temporal, exposed as a global Temporal namespace, aims to fix well known issues such as unclear parsing rules, awkward time zone handling, and mutable date arithmetic."
"MDN describes it as a full replacement for Date, with built in time zones and calendars, wall clock conversions, arithmetic, and formatting. One of the biggest practical wins is that developers can represent a date without accidentally smuggling in a time zone and time of day. For example: const start = Temporal.PlainDate.from('2026-02-13'); const end = start.add({ days: 7 }); When time zones matter, the API makes them explicit."
Chrome 144 adds native support for the Temporal API, exposed as a global Temporal namespace, bringing a modern date and time API to the web. Temporal provides distinct types for distinct jobs, immutable operations that return new values, built-in time zones and calendars, wall clock conversions, arithmetic, and formatting. The API allows representing plain dates without implicit time zones using Temporal.PlainDate and preserves time zones when needed using ZonedDateTime and Temporal.Now helpers. Developers reacted with relief at replacing Date and third-party libraries, but adoption may be gradual because of inconsistent browser support and the need for framework and library updates.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]