You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Temporal subsumes most of the functionality of Moment.js, but there's a ton of code out there using Moment, and it will take a long time to upgrade to the Temporal API. To make the transition easier, while reducing download size, it'd be great to have an implementation of most of the Moment API in terms of Temporal, if this is possible. Same for Luxon or date-fns.
I'm developing vremel, date utility library for Temporal API (which is heavily inspired by date-fns). It's not a shim and its target is not a compatibility with date-fns, functions accept and return Temporal objects, but most functions behave similarly. So I think migration from date-fns itself will not be so hard.
But I feel that paradigm shift from legacy Date to Temporal API can be very tough for many developers, especially when they deal with an existing large codebase.
Originally from tc39/proposal-temporal#104
Temporal subsumes most of the functionality of Moment.js, but there's a ton of code out there using Moment, and it will take a long time to upgrade to the Temporal API. To make the transition easier, while reducing download size, it'd be great to have an implementation of most of the Moment API in terms of Temporal, if this is possible. Same for Luxon or date-fns.
Link to some experimentation with date-fns: https://github.com/ptomato/temporal-fns/commits/port-to-temporal
The text was updated successfully, but these errors were encountered: