Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moment.js Maintenance Mode Announcement #5573

Closed
calebcartwright opened this issue Sep 19, 2020 · 7 comments · Fixed by #8192
Closed

Moment.js Maintenance Mode Announcement #5573

calebcartwright opened this issue Sep 19, 2020 · 7 comments · Fixed by #8192
Labels
dependencies Related to dependency updates

Comments

@calebcartwright
Copy link
Member

Some interesting news on Moment.js being deprecated (sort of). I don't see a need for any action, at least in the short term, given that they've said they'll continue to address security issues. However, opening for awareness and discussion.

https://momentjs.com/docs/#/-project-status/

We now generally consider Moment to be a legacy project in maintenance mode. It is not dead, but it is indeed done.

In practice, this means:

  • We will not be adding new features or capabilities.
  • We will not be changing Moment's API to be immutable.
  • We will not be addressing tree shaking or bundle size issues.
  • We will not be making any major changes (no version 3).
  • We may choose to not fix bugs or behavioral quirks, especially if they are long-standing known issues.

However, since we understand that Moment is well established in millions of existing projects:

  • We will address critical security concerns as they arise.
  • We will release data updates for Moment-Timezone following IANA time zone database releases.
@calebcartwright calebcartwright added the dependencies Related to dependency updates label Sep 19, 2020
@chris48s
Copy link
Member

Yeah I also spotted this the other day. I'd agree with your perspective. There is no rush to migrate given it will continue to receive security updates. That said, our usage of moment is pretty light: we require it in less than 10 files, we're not heavily tied to it by another dependency which forces us to use it, and its not part of our service framework so if we do want to migrate to something else its not an enormous job like request is, for example.

@paulmelnikow
Copy link
Member

Yea, it should be an easy swap.

I'm curious, does anyone have experience with Day.js or the other alternatives?

@calebcartwright
Copy link
Member Author

I'm curious, does anyone have experience with Day.js or the other alternatives?

Nope, I've only ever used Moment

@chris48s
Copy link
Member

this might be a useful resource for removing our reliance on this https://github.com/you-dont-need/You-Dont-Need-Momentjs

@calebcartwright
Copy link
Member Author

Nearly 2 years on and updates are still coming (albeit small and far between) #8170

@chris48s
Copy link
Member

Yes - moment does still receive major bugfixes, just not active development. It is one of the reasons why migrating away from it has fallen by the wayside (another being that it is not completely obvious what to migrate to ).

@DenverCoder1
Copy link
Contributor

dayjs has a very similar API to moment so is likely the easiest to migrate to. I've migrated from moment to dayjs before and for many things it's as simple as just replacing moment() with dayjs().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Related to dependency updates
Projects
None yet
4 participants