dayjs VS moment-timezone

As web developers, we heavily rely OSS packages. One popular example is Day.js, a JS lib for parsing, validating, manipulating, and formatting dates. It's a widely-used alternative to Moment, with over 17mil weekly downloads on npm.

A critical bug was discovered in Day.js (see: https://github.com/iamkun/dayjs/pull/2118) causing incorrect date manipulation (add, subtract) when in UTC TZ. This could have severe implications for any project relying on Day.js for date-related functionality. However, the maintainer of the project appears to be unresponsive, leaving the bug unresolved and the future of the library uncertain.

This raises some important questions for our community:

- At what point should we consider a widely-used OSS project "abandoned" if the maintainer is unresponsive?

- Is forking the project the best solution, or should we first try to reach out to the maintainer through other channels?

- Are there established community guidelines around responsiveness expectations for widely-used OSS projects?

- What are successful examples of community-driven forks or maintenance after a maintainer stepped away?

I am very aware that many of these developers give their spare time for free for these projects, with little or no payment, and I am very thankful for all their work. This developer does get some money (a small amount?) through OpenCollective, and possibly also works for a company (in China?) that makes a UI library, which I think uses Day.js internally.

11. DayJs

DayJS has issues with its timezone plugin not compatible with Hermes engine https://github.com/iamkun/dayjs/issues/1942

Date.js

We have to install refine's support packages for React Table and React Hook Form. We are using Tailwind Heroicons for our icons, the Day.js library for time calculations and Recharts library to plot our charts for KPI data. So, run the following and we are good to go:

DayJS is a lightweight and fast JavaScript library for manipulating dates and times. It offers a moment.js-like API but with a much smaller footprint.

I use Day.js in my projects.

well, I haven't reviewed the code, I just checked package.json and I'll suggest you to ditch moment.js Even the creator recommends ditching it. dayjs is a fantastic alternative.

moment-timezone is pretty great. However the moment library is no longer maintained, and there's some complications to its use due to it being mutable. Still works great though.

It was actually much easier to make than I thought it would be, thanks to Moment.

Otherwise... https://momentjs.com/timezone/

The clock is in Javascript. Time zones in JavaScript historically are non-trivial since everything is based on the client clocktime. Fortunately, there is moment.js and moment-timezone-with-data.js that vastly simplify getting the current time at the NYSE. The clock keeps ticking correctly irregardless of which tab is active. I find the clock to be also functional since the WSBoy is worn over where I would usually be wearing my watch.

I used the Moment-Timezone library, which returns, well, all the timezones! Super easy to get started with, just add using npm or yarn to add it, and then add import moment from 'moment-timezone'; to the top of your file.

Moment Timezone | Home