You Don't Need Moment.js

If you are dealing with timestamps from the past (e.g. birthdays via a datepicker that constructs Date objects), then you should watch out for different browsers' inconsistent handling of Daylight Savings Time. Moment is really indispensable here, since it includes a database of past years' DST transition dates. I wrote a blog post about it here: https://illuminatedcomputing.com/posts/2017/11/javascript-ti...

JS has been moving forward with a new Date/Time API called Temporal[1]. I haven't had a chance to use it myself, but a friend dropped Moment.js for it (I think to keep the browser from adjusting the date to the local time). New APIs (and hence, Temporal) are the type of things that if you don't know about, you can easily miss and go straight to a library for. [1]: https://2ality.com/2021/06/temporal-api.html

It’s almost always better to use a standard than grow something at home. When your project gets bigger (which most projects of interest will), the inertia of the homegrown solution will become a detriment and liability. Only simple or novel use cases should be kept as internal libraries, and dates are not simple.