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
Getting Started
Choose the lowest-risk way to evaluate mmntjs in an existing moment.js codebase. `mmntjs/lite` is recommended as the starting entry point for most teams.
Installation
Install mmntjs and choose the right entry point: `mmntjs` (full compat, 179.5KB raw bundled), `mmntjs/lite` (recommended, 55.2KB raw bundled), or `mmntjs/fns` (tree-shakeable standalone helpers).
Lite and fns Usage
`mmntjs/lite` (55.2KB raw bundled) is the recommended default: moment-compatible method chaining. `mmntjs/fns` is an alternative for teams that prefer standalone functions.
Parsing
Explain how parsing compatibility is evaluated and where edge cases require extra scrutiny.
Timezone and parseZone
Clarify what core UTC and fixed-offset behavior is covered and what requires separate timezone support.
Invalid Dates
Make invalid-date behavior explicit, because it affects both UI and business logic edge cases.
Migration Notes
Collect practical notes for teams replacing moment in real systems, not toy examples.
Known Differences
List currently known behavior differences in a way that helps teams assess practical impact.
Reference Paths
Basic Usage
Formatting, parsing, manipulation, and duration examples using `mmntjs/lite`, the recommended entry point for most teams.
Query and Comparison
Document comparison semantics such as diff, isBefore, isAfter, and range checks.
Browser Usage
Document browser loading shapes and what teams should verify in client bundles.
Runtime Support
Summarize supported runtimes and where runtime-specific behavior deserves extra testing.
API Reference
Reserve a clear endpoint for exhaustive API documentation without forcing it into every guide page.