Moment.js Reverses 'No v3' Pledge as AI-Driven Downloads Surge

On August 17, 2026, the Moment.js project reversed its 2020 pledge that there would never be a version 3.0.

The official update states that weekly downloads have grown several times over, driven largely by AI-assisted and agentic software development. The maintainers believe this new usage is real code that users must run and maintain.

What 3.0 Will and Will Not Do

Will do:

Fix bugs that could not be addressed in 2.x because they required breaking changes.

Potentially adjust API behavior, correct output formats, and change bundling.

Remain essentially a maintenance release, not a feature restart.

Will not do:

Add new user-facing features or capabilities.

Restart feature development.

Turn Moment into a new library.

Address tree shaking.

Make the API immutable (this was discussed and rejected).

// Mutable design causes add to mutate the original object
const a = moment()
const b = a.add(7, 'days')
console.log(a === b) // true, not a new object

// To preserve the original value, you must manually clone
const c = a.clone().add(7, 'days')

In short, 3.0 aims to fix what can be fixed under the existing API, not to make Moment a viable choice for new projects. The official guidance remains unchanged: for most new projects, Day.js, date-fns, Luxon, or the native Intl API are more appropriate.

For existing projects, this means the dependency is still being responsibly maintained. Lock your version range, keep up with 2.x maintenance updates, and evaluate migration only after the 3.0 breaking-changes list is published.