PERFORMANCE: Optimize moment.js

[fpurcell]

Look to reduce the data footprint of moment.js.

See #65

[fpurcell]

Slack conversation that inspired this ticket:

BTW, moment.js seemed to be another problematic dependency, size-wise. Any insights to reducing the footprint there?

evansiroky 10 minutes ago
https://www.npmjs.com/package/moment-timezone-data-webpack-plugin
Also: https://github.com/jmblog/how-to-optimize-momentjs-with-webpack

Cole 4 minutes ago
Yeah there is several things you can do with moment to reduce the size. depending on the need they have that new library luxon that is more modern.

fpurcell 3 minutes ago
From Evan's 2nd link, there's also a pointer to https://github.com/iamkun/dayjs (edited)

Cole 2 minutes ago
Yeah I saw that too, I would be interested to know if timezone works with that too

evansiroky 1 minute ago
If we are to replace I will veto anything without timezone support.

fpurcell 1 minute ago
Think it better to try and optimize moment?

evansiroky < 1 minute ago
Yes

fpurcell < 1 minute ago
k ... I'll create a ticket along those lines.

evansiroky < 1 minute ago
there is plenty of timezone data that is no longer needed that can be quickly removed with specifying a start date

---

evansiroky 4 minutes ago
It's still probably a ways out, but there might be a new date/time/timezone API in js itself: https://github.com/tc39/proposal-temporal

Cole 1 minute ago
Thats interesting.. I kind of ties into the direction of luxon https://github.com/moment/luxon/blob/master/docs/why.md seems like some of the functionality is moving into the browser

evansiroky < 1 minute ago
Yeah, I believe some of the maintainers of luxon are behind the tc39 proposal