Temporal API Ships in Chrome 144, Marking a Major Shift for JavaScript Date Handling
Chrome 144 introduces the Temporal API, a modern approach to date and time handling designed to fix long-standing issues with JavaScript’s Date object.
- Sarah Gooding

Chrome 144 has begun rolling out with support for the Temporal API, bringing a long-awaited modern date and time system to JavaScript in a stable Chrome release for the first time. The feature landed this week, prompting renewed attention from JavaScript engine developers and standards contributors after nearly eight years of design and iteration.
Reacting to the release, TC39 delegate Rob Palmer described the scope of the change, commenting that “by many metrics the new Temporal date-time API is the single biggest change to JS ever.”
Temporal is intended as a replacement for JavaScript’s long-standing Date object, which has accumulated decades of quirks around mutability, parsing, time zones, and daylight saving transitions.
The limitations of JavaScript’s Date API have been widely documented over the years. In an article titled "Date is out, Temporal is in," examining why Temporal was needed, developer and writer Mat “Wilto” Marquis described the problem:
Date sucks. It was hastily and shamelessly copied off of Java’s homework in the car on the way to school and it got all the same answers wrong, right down to the name at the top of the page: Date doesn’t represent a date, it represents a time. Internally, dates are stored as number values called time values: Unix timestamps, divided into 1,000 milliseconds — which, okay, yes, a Unix time does also necessarily imply a date, sure, but still: Date represents a time, from which you can infer a date. Gross. Java deprecated their Date way back in 1997, only a few years after JavaScript’s Date was turned loose on the unsuspecting world; meanwhile, we’ve been saddled with this mess ever since.
Rather than representing all date and time concepts through a single mutable object, Temporal introduces a set of distinct types for different use cases, including PlainDate, ZonedDateTime, Instant, and Duration. All Temporal operations return new values instead of mutating existing ones, making date and time logic easier to reason about and less error-prone.
Browser Support Expands Beyond Firefox
#Before Chrome 144, Temporal was already available in Firefox 139. Safari support is currently in development, with early work visible in Safari Technical Preview. With Chrome and Firefox both shipping implementations, Temporal is now usable in two major engines without requiring a polyfill, though cross-browser production use still requires careful consideration.
Chrome’s implementation another example of the increasing collaboration between JavaScript engines. V8’s Temporal support reuses temporal_rs, a Rust-based library originally developed for the Boa JavaScript engine. The same implementation is now shared across Boa, Kiesel, and V8, reducing duplication and helping align behavior across runtimes.
TC39 Is Expected to Consider Temporal for Stage 4 in March 2026
#Despite shipping in multiple browsers, Temporal is not yet a finalized part of the JavaScript language specification. The proposal is currently at Stage 3 of the TC39 process, meaning it is considered complete enough for implementation but still subject to feedback and potential refinement.
The next step toward standardization is a Stage 4 proposal, which TC39 champions expect to pitch at the March 2026 TC39 plenary meeting, scheduled to take place at Google in New York. Reaching Stage 4 would formally add Temporal to the ECMAScript standard.
Until then, the API documentation on MDN remains the primary reference for developers experimenting with Temporal in supported browsers.
JavaScript’s Date API has been a frequent source of bugs since the language’s early days, particularly when dealing with time zones, daylight saving time, and arithmetic involving months or days. These issues have driven widespread adoption of third-party date libraries, many of which exist primarily to compensate for Date’s limitations.
Temporal’s arrival in Chrome Stable is a significant step toward reducing that reliance. While Date will remain part of the platform for backward compatibility, modern JavaScript date and time handling is moving toward explicit types, immutable operations, and predictable behavior across environments.




