Repository navigation
Let's enable Temporal by default #57127
Description
Activity
It would probably be wise to wait until it's been fully shipped unflagged on the web for a bit - maybe for node 25?
Reacted by Gürgün Dayıoğlu and Jan StrnádekEither way. I'm going to prepare a PR but it's fine to let it sit for a bit
Reacted by Jordan Harband, Patrick Leiser, Noah Seltzer and Kirill GroshkovOn one hand, I can't wait for
Temporalto be available, but on the other hand, I can wait and use the polyfill a while longer. So far the experience of enabling flagged features of V8 has been mixed (TLA was a success, the import assertions syntax not so much); given this is fully polifillable, I'm not sure it's worth the risks (although I reckon the risks are very mild at worst).Can someone link to the tracking issue in V8 so we have some information on the progress of the implementation there?
I wonder if it passes the existing test262 tests for Temporal.
- Reacted by Yusuke Miyajima
Yep, I'm fine with waiting a bit but I wanted to at least get it on the radar here. I'm not in any rush to merge it. V8's test coverage on this is currently hovering around the 75% mark but that is expected to increase significantly in the coming couple of months. My current thinking is that we can let the PR sit and look at merging it still as experimental after 24.0.0 is cut in April with a flag to disable it.
I strongly recommend against unflagging Temporal while it is still flagged in V8. The stability of the proposal has no correlation with the quality, stability, and completeness of the implementation in V8 itself. If Node does choose to unflag a feature before V8 thinks it is ready for production, we will not be prioritizing bugs, which will frustrate everyone involved.
Reacted by Jordan Harband, Sebastian Beltran, Artur Gawlik, Pietro Marchini, Hans Ott, Michał Wadas, Rud Wangrungarun, Chengzhong Wu, Rene Hopfe and Carlos FuentesIf we unflag it (which is still far from settled), it wouldn't be until after 24.0.0 at the earliest and would remain in experimental status until v8 unflags it... which is to say we wouldn't actually expect v8 to prioritize bugs beyond whatever y'all are doing now... but conversations like this are precisely why I opened the issue with the proposal, so these things can be discussed.
Reacted by Patrick LeiserCurrent V8 implementation of Temporal API is not only incomplete but based on the outdated proposal. Plenty of normative changes are not reflected to the implementation, which can make users confused.
Even the API surface has changed. FYI Deno patches
Temporalclasses to minimize the deviation on the public API by removing and adding methods and properties.Despite the effort of Deno, not a few issues (including V8 panic) are reported in the issue tracker.
https://github.com/denoland/deno/issues?q=label%3A%22upstream%22%20temporal
Honestly, I feel that V8 implementation is far from 'experimental', rather it's 'draft'.
Reacted by Jordan Harband, Juan José, Patrick Leiser, Michał Wadas and Mikko PorkolaSee https://chromium-review.googlesource.com/c/v8/v8/+/6514659 / v8/v8@f9aac5f
Temporal in V8 is going to require a Rust toolchain.
Reacted by Theo ParisReacted by Marco Ippolito, Sebastian Beltran, Luke Deen Taylor, Hans Ott, Michał Wadas and KisaragiFWIW, Temporal in V8 is nearing completion: we fail a handful of tests, and there's still some work to do, but it's nearing the point where it might get unflagged.
Reacted by James M Snell, Luke Deen Taylor, Mateusz Kadlubowski, Alexei Boronine, PartMan, Jean Pruliere, Johannes Pfrang, Matías Juarez, Ron Korving, Johan Grundberg and 40 more17 remaining items
- Reacted by Efe Karasakal, Dolan Murvihill, Thomas Hunter II, Bluzzi, Madeline Gurriarán, Caleb Jasik and Patt O'BrienReacted by Omer Mecitoglu, Bluzzi, David Braden, Madeline Gurriarán, Pascal Weiland, Caleb Jasik, Ben Scholzen, Patt O'Brien and Dylan Myers
#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-temporalflag.Reacted by Eli and Paul OReacted by Dylan Myers, Paul O and Fibert LoyeeTemporal API reaches Stage 4.
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- added a commit that references this issue
on Apr 13, 2026 Are there any plans to backport Temporal to Node 24? Thank you.
There are not because support is heavily reliant on the version of V8 and the one in Node.js 24 is too old.
Reacted by Ruben Nogueira@richardlau could it be added to 24 by adding temporal_rs?
@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.
Reacted by Jordan Harband and Guillaume Humbert
What is the problem this feature will solve?
The
TemporalAPI 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 inmainWhat is the feature you are proposing to solve the problem?
Enable Temporal by default but still marked as experimental
What alternatives have you considered?
No response