You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Temporal API is nearing completion in TC39 and is largely stable. It is not turned on by default in V8 just yet until it reaches stage 4 but platforms are starting to enable it by default. We ought to be able to go ahead and enable it by default in main
What is the feature you are proposing to solve the problem?
Enable Temporal by default but still marked as experimental
Reacted by Madeline Gurriarán, Stef, Connor Bär, miyaji255, Michiel ter Reehorst, Luke Deen Taylor, Adam Haglund, leah, Sander Blomvågnes, Amanuel Odicho and 35 more
Reacted by Luke Deen Taylor, richardasymmetric, Martin Ždila, Amanuel Odicho, Jordan Harband, Samuel Gaus, Leon Adler, Abdelrahman Awad, Felix Hanken, Kirill Groshkov and 9 more
I think people are actively working on this, the issue is not abandoned for it to need to be "revisited".
Reacted by Antoine du Hamel, Luke Deen Taylor, leah, Michiel ter Reehorst, Rene Hopfe, Podaru Dragos, AFCMS, Eli, Mateusz Stepaniuk, Rafael Santos and 1 more
fwiw we're at a point now where MDN is suggesting that Date is "considered legacy", that it's "baseline widely available", and that users should use Temporal if possible. Just wanted to note as I rewrote a small feature off of that suggestion only to find out it's not actually available in any non-browser runtime yet 🫠
Reacted by Thomas Hunter II, Paul O, ezzabuzaid, Fibert Loyee and james
the Date object is far from being a legacy feature imho as most db connectors still use Date as base type for anything time related. That being said if we don't open Temporal by default, adoption will never start and we'll stay in that state forever 🤷
Reacted by Tierney Cyren, AlexTheMan, Eli, Julio Flores, Fibert Loyee, Vlad Shcherbin and Tommy Huang
I think calling it legacy in the browser in the evergreen environment we now live in makes sense, but calling it legacy in Node.js and other non-browser runtimes does... not, yes. It's also a language feature and not something for us to really make a call on unless the language wants to start warning on usage.
Date is conceptually legacy in an environment the literal instant Temporal appears. That doesn't mean it can ever be removed nor isn't in wide usage. That includes node as well as browsers.
Reacted by Luke Deen Taylor, AlexTheMan, Eli, Bluzzi, leah, Paul-Willy, Théo LUDWIG, Yann Brelière and Kevin-carbontrail
Typescript 7.0 Already shipping new types for temporal.
Reacted by Efe Karasakal, Madeline Gurriarán, chuck-flowers, Eli, Bluzzi, Omer Mecitoglu, Luke Deen Taylor, Patt O'Brien, Cleyton Goncalves, Hein Behrens and 6 more
Reacted by AlexTheMan, Bluzzi, Dylan Myers, Cleyton Goncalves, Caleb Jasik, Madeline Gurriarán, Benjamin DANIEL, Alex Van Dijck, S. Mahdi Mir-Ismaili and Franco Colman Mendoza
#57127 (comment)
Just wanted to note as I rewrote a small feature off of that suggestion only to find out it's not actually available in any non-browser runtime yet 🫠
@bnb: For what it's worth, shortly after that comment was posted, Deno v2.7.0 stabilized it's temporal support (in Deno #31298). As of that reply, Deno did have it behind a --unstable-temporal flag.
Reacted by Dolan Murvihill, richardasymmetric, Inomares, Jordan Harband, Yann Brelière, Jan Iłowski, Pierre-Élie Fauché, Richard EJC, Dylan Myers, Ghislain B. and 35 more
@ljharb I suspect not. At least not without an unknown number of V8 backports (if that is even practical). The version of V8 in Node.js 24 is pre-temporal_rs.
Activity
y-nk commentedon Nov 4, 2025
how to enable it in the meantime?
targos commentedon Nov 4, 2025
There's no built-in way to do it. I would suggest to use a polyfill in the meantime.
checkmatez commentedon Nov 5, 2025
Temporal is unflagged in V8 today - https://issues.chromium.org/issues/401065166#comment106
Heading for Chrome 144.
y-nk commentedon Nov 10, 2025
@targos that's what i figured in the end. i went for https://github.com/js-temporal/temporal-polyfill/ which looks like "the official" implementation. thank you for the answer (and sorry for answering back late)
PodaruDragos commentedon Dec 11, 2025
Temporalwill now ship inchrome144betaas seen here blog. So is this a good time to revisit this issue ?Manishearth commentedon Dec 11, 2025
I think people are actively working on this, the issue is not abandoned for it to need to be "revisited".
bnb commentedon Feb 11, 2026
fwiw we're at a point now where MDN is suggesting that Date is "considered legacy", that it's "baseline widely available", and that users should use Temporal if possible. Just wanted to note as I rewrote a small feature off of that suggestion only to find out it's not actually available in any non-browser runtime yet 🫠
controversial commentedon Feb 11, 2026
@bnb the “baseline widely available” note in your screenshot refers to Date, not to Temporal. Temporal is not baseline widely available.
bnb commentedon Feb 11, 2026
ah fair, mistake on my end.
y-nk commentedon Feb 12, 2026
the Date object is far from being a legacy feature imho as most db connectors still use Date as base type for anything time related. That being said if we don't open Temporal by default, adoption will never start and we'll stay in that state forever 🤷
bnb commentedon Feb 12, 2026
I think calling it legacy in the browser in the evergreen environment we now live in makes sense, but calling it legacy in Node.js and other non-browser runtimes does... not, yes. It's also a language feature and not something for us to really make a call on unless the language wants to start warning on usage.
ljharb commentedon Feb 12, 2026
Date is conceptually legacy in an environment the literal instant Temporal appears. That doesn't mean it can ever be removed nor isn't in wide usage. That includes node as well as browsers.
efekrskl commentedon Feb 13, 2026
Chrome 144 was released with the Temporal API
Edit: whoops, it was released a month ago
Manishearth commentedon Feb 13, 2026
(Chrome 144 was released a month ago)
randreu28 commentedon Mar 7, 2026
https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/#new-types-for-temporal
Typescript 7.0 Already shipping new types for temporal.
ctcpip commentedon Mar 11, 2026
https://bsky.app/profile/tc39.es/post/3mgsa4jzers2x
dmpmem commentedon Mar 16, 2026
@bnb: For what it's worth, shortly after that comment was posted, Deno v2.7.0 stabilized it's temporal support (in Deno #31298). As of that reply, Deno did have it behind a
--unstable-temporalflag.paulo-assoc commentedon Mar 25, 2026
Temporal API reaches Stage 4.
build: enable Temporal by default
build,win: fix Temporal build
build,win: fix Temporal build
build: enable Temporal by default
build,win: fix Temporal build
build: enable Temporal by default
Temporaljames-pre/axium#10rubnogueira commentedon May 20, 2026
Are there any plans to backport Temporal to Node 24? Thank you.
richardlau commentedon May 20, 2026
There are not because support is heavily reliant on the version of V8 and the one in Node.js 24 is too old.
ljharb commentedon May 20, 2026
@richardlau could it be added to 24 by adding temporal_rs?
richardlau commentedon May 20, 2026
@ljharb I suspect not. At least not without an unknown number of V8 backports (if that is even practical). The version of V8 in Node.js 24 is pre-temporal_rs.