![]() ![]() Some libraries are split into modules, plugins, or companion libraries.There are several great options to consider using instead of Moment. If so, and the aforementioned issues are not a concern for you, then you certainly can continue to use it. If you are a long-time user of Moment, you may already understand its API and limitations well. Thus, it might make sense to continue using Moment throughout your project rather than including yet another date and time library. If you are using such a component and cannot find an alternative, then you are already including Moment in your project. Several other libraries, especially date pickers and graphing libraries, take Moment as a dependency. However, Day.js reports compatibility with IE8 and higher so you still may wish to consider that alternative. If you have a strong requirement to support older browsers, then you might want to stick with Moment for a bit longer. ![]() Other libraries have also had issues with Safari, especially on mobile devices. ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |