proposal-temporal VS Luxon

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

To be honest, use a library where someone else figured out the ambiguities and accounted for the edge cases. Good starting point: https://moment.github.io/luxon/#/math

Date-fns is fine for simpler use cases but Luxon is a lot more complete, especially where it comes to time zones.

8. Luxon: Mastering Time and Timezones for Precision Data Handling

In past i used Moment, but I read that we should avoid to use it for future projects. I read someone suggested to use Datejs, but it doesn't seems to be updated, last time was 8 years ago. Currently I'm thinking to use Luxon but I someone suggest Date-fns also.

Pain

I haven't seen this before, but I currently use Luxon most of the time and it makes working with dates and times a lot less painful.

Eleventyone’s project scaffold includes: Eleventy with a skeleton site, a date format filter for Nunjucks based on Luxon, a tiny CSS pipeline with PostCSS, an equally tiny inline JS pipeline, JS search index generator, Netlify Dev for testing Netlify redirects, and a serverless (FaaS) development pipeline with Netlify Dev and Netlify Functions.

Luxon is a powerful and lightweight JavaScript library for working with dates and times. It was created as an alternative to the popular Moment.js library, with the goal of being faster, smaller, and easier to use.

If you ever wondered how luxon and native JS-Dates (with TimeZones) behave when converting them between each other and ISO-Date-Strings here are my tests:

But how does this compare to Luxon? (https://moment.github.io/luxon/#/why)