Skip to content

Let's enable Temporal by default #57127

Closed

Description

@jasnell

What is the problem this feature will solve?

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

What alternatives have you considered?

No response

Activity

  1. y-nk commented on Nov 4, 2025

    @y-nk

    how to enable it in the meantime?

  2. targos commented on Nov 4, 2025

    @targos
    Member

    There's no built-in way to do it. I would suggest to use a polyfill in the meantime.

  3. checkmatez commented on Nov 5, 2025

    @checkmatez

    Temporal is unflagged in V8 today - https://issues.chromium.org/issues/401065166#comment106
    Heading for Chrome 144.

  4. y-nk commented on Nov 10, 2025

    @y-nk

    @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)

  5. PodaruDragos commented on Dec 11, 2025

    @PodaruDragos

    Temporal will now ship in chrome144beta as seen here blog. So is this a good time to revisit this issue ?

  6. Manishearth commented on Dec 11, 2025

    @Manishearth
    Contributor

    I think people are actively working on this, the issue is not abandoned for it to need to be "revisited".

  7. bnb commented on Feb 11, 2026

    @bnb
    Contributor

    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 🫠

    Image
  8. controversial commented on Feb 11, 2026

    @controversial

    @bnb the “baseline widely available” note in your screenshot refers to Date, not to Temporal. Temporal is not baseline widely available.

  9. bnb commented on Feb 11, 2026

    @bnb
    Contributor

    ah fair, mistake on my end.

  10. y-nk commented on Feb 12, 2026

    @y-nk

    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 🤷

  11. bnb commented on Feb 12, 2026

    @bnb
    Contributor

    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.

  12. ljharb commented on Feb 12, 2026

    @ljharb
    SponsorMember

    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.

  13. efekrskl commented on Feb 13, 2026

    @efekrskl
    Member

    Chrome 144 was released with the Temporal API

    Edit: whoops, it was released a month ago

  14. Manishearth commented on Feb 13, 2026

    @Manishearth
    Contributor

    (Chrome 144 was released a month ago)

  15. randreu28 commented on Mar 7, 2026

    @randreu28
  16. ctcpip commented on Mar 11, 2026

    @ctcpip
  17. dmpmem commented on Mar 16, 2026

    @dmpmem

    #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.

  18. paulo-assoc commented on Mar 25, 2026

    @paulo-assoc

    Temporal API reaches Stage 4.

  19. added a commit that references this issue on Apr 13, 2026
  20. added a commit that references this issue on Apr 13, 2026
  21. rubnogueira commented on May 20, 2026

    @rubnogueira
    Contributor

    Are there any plans to backport Temporal to Node 24? Thank you.

  22. richardlau commented on May 20, 2026

    @richardlau
    Member

    There are not because support is heavily reliant on the version of V8 and the one in Node.js 24 is too old.

  23. ljharb commented on May 20, 2026

    @ljharb
    SponsorMember

    @richardlau could it be added to 24 by adding temporal_rs?

  24. richardlau commented on May 20, 2026

    @richardlau
    Member

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions