@multisystemsuite/timezone-engine-world-data

@multisystemsuite/timezone-engine-world-data

Offline-first timezone, country, city, and locale metadata registry. No network required at runtime.

What it is used for

• Offline IANA timezone lookup when CDN/network is unavailable
• Country → timezone mapping (IN → Asia/Kolkata)
• City → timezone mapping (mumbai → Asia/Kolkata)
• Locale date/time format preferences (IN, US, EU, UK, JP, AR, CN)
• Date format registry (ISO, SHORT, LONG, etc.)
• Docker, edge, and air-gapped enterprise deployments

Install

npm install @multisystemsuite/timezone-engine-world-data

Usage

import {
  getTimezoneInfo,
  getCountryTimezones,
  getCityTimezone,
  listAllTimezones,
  getLocaleMetadata,
  getRegionalPattern,
  LOCALE_METADATA,
  TIMEZONE_REGISTRY,
} from "@multisystemsuite/timezone-engine-world-data";

const india = getCountryTimezones("IN");
// { countryCode: "IN", defaultTimezone: "Asia/Kolkata", ... }

const mumbai = getCityTimezone("mumbai");
// { city: "Mumbai", timezone: "Asia/Kolkata" }

const info = getTimezoneInfo("Asia/Tokyo");
// { timezone, country, utcOffset, dst, locale, ... }

const pattern = getRegionalPattern("IN"); // "dd/MM/yyyy"

Subpath exports

import { TIMEZONE_REGISTRY } from "@multisystemsuite/timezone-engine-world-data/timezones";
import { COUNTRY_TIMEZONE_MAP } from "@multisystemsuite/timezone-engine-world-data/countries";
import { LOCALE_METADATA } from "@multisystemsuite/timezone-engine-world-data/locales";

Supported regions (sample)

Asia/Kolkata, America/New_York, Europe/London, Asia/Tokyo, Australia/Sydney, UTC, and 30+ more. Full IANA validation falls back to the runtime Intl API.

Related packages

• @multisystemsuite/timezone-engine-core — uses this data for formatting
• @multisystemsuite/timezone-engine-shared-types — TimezoneInfo, LocaleMetadata types

Keywords

timezone, iana, world-data, locale, countries, cities, offline, metadata

License

MIT