You can read more in Luxon's documentation. By contrast, Luxon only works on IE 10 and higher and requires a polyfill to do so. Moment works well on Internet Explorer 8 and higher.

However there are some possible reasons you might want to keep using it. In most cases, you should not choose Moment for new projects. We will release data updates for Moment-Timezone following IANA time zone database releases.We will address critical security concerns as they arise.However, since we understand that Moment is well established in millions of existing projects: If the string or format you are asking to change is reflected in the CLDR, then you must submit a change there first and have it accepted.You must make a new compelling argument for locale changes with significant, non-anecdotal evidence to support your position.We may choose to not accept corrections to locale strings or localized date formats, especially if they have been argued successfully for their present form.With specific regard to Moment's internationalization locale files: We may choose to not fix bugs or behavioral quirks, especially if they are long-standing known issues.We will not be making any major changes (no version 3).We will not be addressing tree shaking or bundle size issues.We will not be changing Moment's API to be immutable.We will not be adding new features or capabilities.We now generally consider Moment to be a legacy project in maintenance mode. We would also like to promote the Temporal addition to the JavaScript language, which is looking for feedback and contributors. Instead, we would like to recommend alternatives that are excellent choices for use in modern applications today. We recognize that many existing projects may continue to use Moment, but we would like to discourage Moment from being used in new projects going forward. The Moment team has discussed these issues at length. 4 alternatives to moment.js for internationalizing dates.You Probably Don't Need Moment.js Anymore.Recently, Chrome Dev Tools started showing recommendations for replacing Moment for the size alone. Libraries like Luxon (and others) take advantage of this, reducing or removing the need to ship your own data files. Modern web browsers (and Node.js) expose internationalization and time zone support via the Intl object, codified as ECMA-402.

If one needs internationalization or time zone support, Moment can get quite large. Moment doesn't work well with modern 'tree shaking' algorithms, so it tends to increase the size of web application bundles. Since this has already been accomplished in other libraries, we feel that it is more important to retain the mutable API.Īnother common argument against using Moment in modern applications is its size. We address it in our usage guidance but it still comes as a surprise to most new users.Ĭhanging Moment to be immutable would be a breaking change for every one of the projects that use it.Ĭreating a 'Moment v3' that was immutable would be a tremendous undertaking and would make Moment a different library entirely. This is a common source of complaints about Moment. Given how many projects depend on it, we choose to prioritize stability over new features.Īs an example, consider that Moment objects are mutable. Moment has evolved somewhat over the years, but it has essentially the same design as it did when it was created in 2011. The modern web looks much different these days. Moment.js has been successfully used in millions of projects, and we are happy to have contributed to making date and time better on the web.Īs of September 2020, Moment gets over 12 million downloads per week! However, Moment was built for the previous era of the JavaScript ecosystem.

Moment js change date format