Upgrades and deprecations
Moment JS Alternatives: date-fns, Luxon, Day.js or Temporal
In short
Picking among Moment JS alternatives is mostly a decision about time zones and about how much of your code silently relies on Moment's mutable objects. Day.js is the shortest hop for Moment-style code. Luxon suits zone-heavy apps. date-fns suits code built on plain Date. Temporal is a finished standard, but the browser support you need is not there yet.
Is Moment deprecated, or just finished?
Neither word is quite what the maintainers use. Their September 2020 status post called Moment a legacy project in maintenance mode, not dead but done, and discouraged it for new projects. It ruled out an immutable API, work on tree shaking and bundle size, and any version 3.
An update dated 17 August 2026 changed part of that. It keeps the legacy label and still refuses new user-facing features or a redesign of the mutable API. It now says a 3.0 is no longer ruled out, purely as a maintenance release where semver demands a major number, with no schedule announced. It also lists bundle composition and TypeScript declarations among work maintainers may take on, and it says Moment Timezone data keeps following IANA releases.
The registry shows the result: moment 2.31.0 was published on 15 September 2026, and the package carries no npm deprecation flag. The 2026 post says weekly downloads have more than tripled since 2020 and links most of that growth to coding agents choosing Moment by default. That is a reason to check new dependencies, not a sign the library changed direction.
What does each replacement's own documentation promise?
The three libraries answer the same three questions differently: whether a value can change under you, where time zone rules come from, and how locale data reaches the bundle.
date-fns
The README describes pure functions over the native Date type that always return a new instance, and it says the package supports tree shaking. The latest release on the registry is 4.4.0.
Time zones arrived in v4 through two separate packages, @date-fns/tz and @date-fns/utc, used either as TZDate values or through an in option on the functions. Before v4 the docs point to a third-party package. Locales are imported one by one and passed per call, and only four formatting functions take them: format, formatDistance, formatDistanceStrict and formatRelative.
Luxon
Luxon was written by a Moment maintainer as a rethink rather than a patch. Its Moment guide says every object is immutable, so plus() hands back a new value where Moment's add() changed the original.
Zones and locale strings come from the runtime's Intl API, with no plugin and no bundled zone data. The same guide warns that months are 1-indexed, that parsers are strict where Moment was lenient, and that arguments are not coerced into Luxon objects. Its Intl page tells Node users to make sure the runtime has ICU data.
Day.js
Day.js sells itself on a largely Moment-compatible API and lists immutability among its features. Its install page says the CI matrix still includes IE 8, 9 and 10.
Time zones need two plugins, utc and timezone, extended onto the core. The docs say they use the Intl API so no zone data ships in your bundle, and they ask for a polyfill on older runtimes. Locales load on demand, either globally or per instance.
Checked against: source 4, source 5, source 6, source 7, source 8, source 9, source 10, source 11, source 12, source 13, source 14
Where does Temporal stand today?
The proposal's README says Temporal is at Stage 4 and will be merged into ECMA-262 and ECMA-402. TC39's finished-proposals table lists it with an expected publication year of 2027 and links the March 2026 meeting notes headed Temporal for Stage 4.
Engines are partly there. The README records shipping in Firefox 139 on 27 May 2025, Chrome 144 on 13 January 2026 and Node 26 on 5 May 2026. Its Safari entry links a WebKit bug with no shipped release named.
MDN still marks Temporal as Limited availability and says it is not Baseline because it fails in some widely used browsers. MDN describes it as designed to fully replace Date, and the proposal states that all Temporal objects are immutable. For browser code today, that means either a polyfill or waiting.
Which Moment JS alternatives fit which situation?
Read this as a sorting aid built on the documents above, not a ranking. The situation decides, and the first match wins.
- Large Moment codebase, little time: Day.js, because its API is the closest documented match. Audit every place that relied on mutation, since chained calls now return copies.
- Scheduling across named zones, DST edge cases, durations and intervals: Luxon, which builds zones in and documents Interval and Duration types.
- Code that already passes plain Date objects around, or a team that wants tree shaking per function: date-fns 4 with
@date-fns/tzwhere zones matter. - Server-side or a controlled runtime such as Node 26: try Temporal directly for new modules and keep a library at the edges.
- A date picker or chart library that depends on Moment: the 2020 post itself names this as a reason to keep Moment rather than ship two date libraries.
- Old browsers you must support: Moment's 2020 post cites IE support as a reason to stay, and points to Day.js as an option that reports IE 8 compatibility.
Checked against: source 1, source 2, source 4, source 7, source 8, source 11, source 12, source 13, source 16
What usually goes wrong in the swap?
Mutation is the silent one. Moment code often works because some helper changed a shared object. Every replacement here returns a new value instead, so a call whose result is thrown away now does nothing, with no error.
Zones are the loud one. Without the utc and timezone plugins, Day.js formats in the machine's local zone, and a UTC timestamp can land on the wrong calendar day; this fix page covers that case. In Luxon the month off-by-one runs the other way, because January is 1.
Version drift is the third. date-fns changed how functions are exported between majors, and this page shows the adapter mismatch it causes. If Moment arrives through a wrapper, this page explains why it still has to be installed.
What else do people ask?
Does the 2026 Moment update mean it is safe to start new projects with it?
The update keeps the legacy, maintenance-mode label and still refuses new features. It changes what maintenance may include, not the advice about new work.
Can I use Temporal without a library today?
Where the engine ships it, such as Chrome 144, Firefox 139 or Node 26 per the proposal README. MDN still lists it as Limited availability, so browser code that must run everywhere needs a fallback.
Sources
- Moment.js news, Project Status Update (17 August 2026), fetched 2026-11-20
- Moment.js, Project Status (14 September 2020), source file, fetched 2026-11-20
- npm registry, moment versions and publish dates, fetched 2026-11-20
- Luxon docs, For Moment users, fetched 2026-11-20
- Luxon docs, Why does Luxon exist, fetched 2026-11-20
- Luxon docs, Intl, fetched 2026-11-20
- Day.js README, fetched 2026-11-20
- Day.js docs, Time Zone, fetched 2026-11-20
- Day.js docs, Loading locale in the browser, fetched 2026-11-20
- Day.js docs, Installation, fetched 2026-11-20
- date-fns README, fetched 2026-11-20
- date-fns docs, Time zones, fetched 2026-11-20
- date-fns docs, Internationalization, fetched 2026-11-20
- npm registry, date-fns latest version, fetched 2026-11-20
- MDN, Temporal, fetched 2026-11-20
- TC39, Temporal proposal README (status and implementations), fetched 2026-11-20
- TC39, Finished Proposals, fetched 2026-11-20
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page compares project documents I fetched on 20 Nov 2026 (Moment's status posts, the npm registry, the Luxon, Day.js and date-fns docs, MDN and TC39). I did not port any code for it. It gives no bundle sizes and does not cover js-Joda, date pickers or your own call sites. Found a mistake? Tell me.