js-joda VS proposal-temporal

js-joda

So first, a simple example of how this works. Using our "What is your birthday" example, we can mock up this code. Note: I'm using TypeScript because it enforces the concepts at compile time, but the JsJoda library itself enforces the concepts at runtime so that we get the best of both.

Dealing with human dates is non-trivial thanks to localization. The easiest thing to do is to start with something zone agnostic (like UTC or epoch) do your date calculation, and then shift that into the locale you want. date-fns is fine for basic date math, but if you want something more robust, with a more cohesive API, I'd recommend js-joda.

How come the js-joda library is never mentioned in discussions about javascript date/time libraries? its API is perfect and it has been around forever. but instead the community seems to keep inventing more and more new datetime libraries. i don't understand why js-joda seems to be ignored

https://js-joda.github.io/js-joda/

I've been getting by with js joda. Temporal is a welcome addition.

Support for the domain models LocalDate, LocalDateTime, ZonedDateTime, Instant, Duration and Period. Also, supports IANA timezone, adding the plugin @js-joda/timezone you'll have access to the IANA timezone database with all the timezones available.

In the TypeScript/JavaScript world the only thing called "Temporal" that I was aware of is the Stage 3 proposal for an excellent new date and time module:

https://tc39.es/proposal-temporal/docs/

Time Zone Canonicalization: Stacked on Temporal to improve handling of changes to the IANA Time Zone Database.

Roll-on Temporal!

There is a list of polyfills at the bottom of the page that can be used in production. https://github.com/tc39/proposal-temporal