Support `temporal` TC39 proposal
See original GitHub issue- FakeTimers version : 6.0.1
- Environment : N/A
- Example URL : N/A
- Other libraries you are using: None
Repo: https://github.com/tc39/proposal-temporal/
We should support faking out usage of all Temporal.now.*
methods. Not sure if we need to fake anything else?
Note that I do not think we should support Temporal
now - the proposal is still at stage 2. So consider this more of a tracking issue than something that’s actionable right now.
What did you expect to happen? N/A
What actually happens N/A
How to reproduce N/A
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6 (5 by maintainers)
Top Results From Across the Web
tc39/proposal-temporal: Provides standard objects ... - GitHub
Temporal. Provides standard objects and functions for working with dates and times. Status. This proposal is currently Stage 3 and was reviewed for...
Read more >Temporal documentation - TC39
This is a proposal for Temporal , a global Object that acts as a top-level namespace (like Math ), that brings a modern...
Read more >Temporal in ECMA262 - Chrome Platform Status
Temporal API https://github.com/tc39/proposal-temporal in ECMA262 is a new API that provides standard objects and functions for working with ...
Read more >proposal-temporal - npm
Experimental polyfill for the TC39 Temporal proposal. Latest version: 0.9.0, last published: a year ago. Start using proposal-temporal in ...
Read more >Temporal: getting started with JavaScript's new date time API
The ECMAScript proposal “Temporal” is a new and better date time API and currently at stage 3. It was created by Philipp Dunkel, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is stage 3, but will not be shipped unflagged at this time, so it’ll be awhile.
You will only have to mock out
Temporal.now
, by design.I would start implementing now, but perhaps hold off shipping it until at least one engine has landed it, or at least until a production-ready spec-compliant polyfill exists.
Wonderful 👍
If somebody is up for implementing it, I think we can also ship it as long as it’s clearly marked as unstable in docs and possibly code, e.g.
unstable_enableTemporalSupport: boolean
or something. Not sure, and I don’t feel strongly