Docs

Documentation organized for migration risk.

The docs prioritize the questions large codebases ask first: what is compatible, what is risky, what to test, and how to roll out incrementally.

Start Here

Choose the lowest-risk way to evaluate mmntjs in an existing moment.js codebase.

Install mmntjs as a standalone package or as a moment-compatible replacement.

Use `mmntjs/lite` when bundle size matters and you want to add back only the pieces you need.

Explain how parsing compatibility is evaluated and where edge cases require extra scrutiny.

Clarify what core UTC and fixed-offset behavior is covered and what requires separate timezone support.

Make invalid-date behavior explicit, because it affects both UI and business logic edge cases.

Collect practical notes for teams replacing moment in real systems, not toy examples.

List currently known behavior differences in a way that helps teams assess practical impact.

Reference Paths

Formatting, parsing, manipulation, and duration examples without diving into API reference detail.

Document comparison semantics such as diff, isBefore, isAfter, and range checks.

Document browser loading shapes and what teams should verify in client bundles.

Summarize supported runtimes and where runtime-specific behavior deserves extra testing.

Reserve a clear endpoint for exhaustive API documentation without forcing it into every guide page.