mmntjs
Compatibility-first migration bridge away from moment.js

Docs

Timezone and parseZone

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

Guidance

Timezone Expectations Need Plain Language

The site should clearly separate core UTC and fixed-offset behavior from full timezone-data expectations. Most costly migration mistakes happen when teams assume these are the same concern.

  • Verify parseZone and keepLocalTime with real examples.
  • Run tests in at least one non-UTC timezone.
  • Document any dependence on external timezone data explicitly.

How To Use This Doc

Use this page as a migration review aid rather than as a generic tutorial. If the behavior in this area is business-critical, compare it directly against your current moment.js usage and record the outcome before expanding rollout.