JavaScript Temporal API Ships in Chrome
What happened
The long-awaited Temporal API has shipped in Chrome 144, providing a modern and standardized way to handle dates and times in JavaScript. This new global object is intended to replace the existing `Date` object and reduce reliance on third-party libraries like moment.js. The API aims to offer cleaner, more predictable code for frontend developers dealing with time zones, calendars, and date arithmetic.
Why it matters
- The legacy `Date` object, largely unchanged for nearly 30 years, was based on Java's original, flawed `java.util.Date` and is notoriously problematic; its issues include mutability which can lead to hard-to-trace bugs, unreliable string parsing, and poor time zone support. - One of the most significant advantages of the Temporal API is immutability; unlike the old `Date` object which can be changed by functions, all Temporal objects are immutable, preventing unexpected side effects in applications. - The proposal for the Temporal API reached Stage 3 in the TC39 process in March 2021, signaling that the design was stable and ready for browsers to implement. Firefox was the first browser to ship a complete implementation in version 139 in May 2025. - Temporal introduces a suite of new, purpose-specific objects to handle different use cases, such as `Temporal.PlainDate` for a date without time or time zone, `Temporal.PlainTime` for a time without a date, and `Temporal.ZonedDateTime` for handling time-zone-aware dates. - The API is designed to reduce reliance on large third-party libraries like Moment.js or date-fns, which developers have historically used to work around the shortcomings of the `Date` object. Being a native browser API, it also offers performance benefits by not adding to a project's bundle size. - While Chrome and Firefox now have full support, Safari's implementation is still in progress, tracked under WebKit bug 223166. For cross-browser compatibility during this transition, polyfills like `@js-temporal/polyfill` are available for developers. - Discussions within the developer community on platforms like Hacker News show a long-held frustration with the `Date` object and a strong sense of relief and enthusiasm for a standardized, modern replacement.
Key numbers
- The long-awaited Temporal API has shipped in Chrome 144, providing a modern and standardized way to handle dates and times in JavaScript.
- The proposal for the Temporal API reached Stage 3 in the TC39 process in March 2021, signaling that the design was stable and ready for browsers to implement.
- Firefox was the first browser to ship a complete implementation in version 139 in May 2025.
- While Chrome and Firefox now have full support, Safari's implementation is still in progress, tracked under WebKit bug 223166.
What happens next
- Firefox was the first browser to ship a complete implementation in version 139 in May 2025.
- The API aims to offer cleaner, more predictable code for frontend developers dealing with time zones, calendars, and date arithmetic.
Quick answers
What happened in JavaScript Temporal API Ships in Chrome?
The long-awaited Temporal API has shipped in Chrome 144, providing a modern and standardized way to handle dates and times in JavaScript. This new global object is intended to replace the existing Date object and reduce reliance on third-party libraries like moment.js. The API aims to offer cleaner, more predictable code for frontend developers dealing with time zones, calendars, and date arithmetic.
Why does JavaScript Temporal API Ships in Chrome matter?
The legacy Date object, largely unchanged for nearly 30 years, was based on Java's original, flawed java.util.Date and is notoriously problematic; its issues include mutability which can lead to hard-to-trace bugs, unreliable string parsing, and poor time zone support. One of the most significant advantages of the Temporal API is immutability; unlike the old Date object which can be changed by functions, all Temporal objects are immutable, preventing unexpected side effects in applications. The proposal for the Temporal API reached Stage 3 in the TC39 process in March 2021, signaling that the design was stable and ready for browsers to implement. Firefox was the first browser to ship a complete implementation in version 139 in May 2025. Temporal introduces a suite of new, purpose-specific objects to handle different use cases, such as Temporal.PlainDate for a date without time or time zone, Temporal.PlainTime for a time without a date, and Temporal.ZonedDateTime for handling time-zone-aware dates. The API is designed to reduce reliance on large third-party libraries like Moment.js or date-fns, which developers have historically used to work around the shortcomings of the Date object. Being a native browser API, it also offers performance benefits by not adding to a project's bundle size. While Chrome and Firefox now have full support, Safari's implementation is still in progress, tracked under WebKit bug 223166. For cross-browser compatibility during this transition, polyfills like @js-temporal/polyfill are available for developers. Discussions within the developer community on platforms like Hacker News show a long-held frustration with the Date object and a strong sense of relief and enthusiasm for a standardized, modern replacement.
