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
Currently, Charlie uses Moment.js for all date, time, and timezone-based functionality because honestly, who wants to code all that stuff from scratch? No thanks. However, Moment.js is being retired, eventually in favor of the upcoming Temporal global object. In the interim, the Moment.js team has some recommendations for replacements.
investigate alternatives
pick one
decide when to make the switch (i.e., do we wait for Temporal? Find a reasonable polyfill? etc.)
do the switching of the thing
The text was updated successfully, but these errors were encountered:
Temporal is still probably on track for ratification this summer. It would then need to be released in V8 and that V8 update would need to be picked up by Node.js. The V8 team is already working on it, but I wouldn't expect it to land in Node.js before v20 in fall of 2023.
It might be worth finishing up #321 and merging that. Relying on the polyfill isn't the worst thing we could do, and switching to native support when it becomes available ought to be pretty trivial (just take out the polyfill!).
Currently, Charlie uses Moment.js for all date, time, and timezone-based functionality because honestly, who wants to code all that stuff from scratch? No thanks. However, Moment.js is being retired, eventually in favor of the upcoming Temporal global object. In the interim, the Moment.js team has some recommendations for replacements.
The text was updated successfully, but these errors were encountered: