@northguild/gmt 1.19.0 → 1.20.0

package/dist/plain/interval/intervalsOverlapDate.d.ts

@@ -10,7 +10,7 @@
  * - Returns `false` if either interval is invalid (`start > end`).
  * - Returns `false` on invalid input (wrong type, malformed strings).
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Ordering is
- *   calendar-independent, so arguments may carry different or no calendar tags (D4).
+ *   calendar-independent, so arguments may carry different or no calendar tags.
  * - Compatibility: since 1.16.0 calendar strings are RFC 9557 (ISO digits, `[u-ca=<id>]`, canonical
  *   calendar ids); see `isValidCalendarDate`.
  *

package/dist/plain/interval/intervalsOverlapDate.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { halfOpenOverlap, parseCalendarDateValue } from "../../internal/index.js";
 import { isValidCalendarDate } from "../validate/index.js";
 /**
@@ -14,7 +14,7 @@ import { isValidCalendarDate } from "../validate/index.js";
  * - Returns `false` if either interval is invalid (`start > end`).
  * - Returns `false` on invalid input (wrong type, malformed strings).
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Ordering is
- *   calendar-independent, so arguments may carry different or no calendar tags (D4).
+ *   calendar-independent, so arguments may carry different or no calendar tags.
  * - Compatibility: since 1.16.0 calendar strings are RFC 9557 (ISO digits, `[u-ca=<id>]`, canonical
  *   calendar ids); see `isValidCalendarDate`.
  *

package/dist/plain/interval/intervalsOverlapDateTime.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { halfOpenOverlap } from "../../internal/index.js";
 import { isValidDateTime } from "../validate/index.js";
 /**

package/dist/plain/interval/intervalsOverlapTime.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { halfOpenOverlap } from "../../internal/index.js";
 import { isValidTime } from "../validate/index.js";
 /**

package/dist/plain/interval/mergeIntervalsDate.d.ts

@@ -14,7 +14,7 @@
  *   `start > end`.
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Since the result is
  *   date *values*, every `start`/`end` across the whole list must carry the *same* calendar tag
- *   (or all be bare ISO); any mismatch returns `[]` (E5 decision of record D4).
+ *   (or all be bare ISO); any mismatch returns `[]`.
  *
  * @param intervals array of `{ start, end }` records, optionally calendar-annotated
  * @returns the minimum set of non-overlapping `{ start, end }` records, sorted by start, or `[]` on invalid input / mismatched calendars

package/dist/plain/interval/mergeIntervalsDate.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { calendarOfAllDateValues, formatDateInCalendar, halfOpenMerge, parseCalendarDateValue, } from "../../internal/index.js";
 import { isValidDateInterval } from "./validate/index.js";
 import { isObject } from "../../internal/isObject.js";
@@ -18,7 +18,7 @@ import { isObject } from "../../internal/isObject.js";
  *   `start > end`.
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Since the result is
  *   date *values*, every `start`/`end` across the whole list must carry the *same* calendar tag
- *   (or all be bare ISO); any mismatch returns `[]` (E5 decision of record D4).
+ *   (or all be bare ISO); any mismatch returns `[]`.
  *
  * @param intervals array of `{ start, end }` records, optionally calendar-annotated
  * @returns the minimum set of non-overlapping `{ start, end }` records, sorted by start, or `[]` on invalid input / mismatched calendars

package/dist/plain/interval/mergeIntervalsDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { halfOpenMerge } from "../../internal/index.js";
 import { isValidDateTimeInterval } from "./validate/index.js";
 import { isObject } from "../../internal/isObject.js";

package/dist/plain/interval/mergeIntervalsTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { halfOpenMerge } from "../../internal/index.js";
 import { isValidTimeInterval } from "./validate/index.js";
 import { isObject } from "../../internal/isObject.js";

package/dist/plain/interval/splitIntervalByUnitDate.d.ts

@@ -10,9 +10,8 @@
  * - Each boundary is computed from `start` (`start + k × amount`), not by stepping from the
  *   previous boundary, so month-end starts don't drift: a monthly split from January 31 lands
  *   on February 29, March 31, April 30. Temporal's `add` constrains a day the month lacks to
- *   the month's last day, and stepping from that boundary would keep the shortened day
- *   (February 29, then March 29).
- * - Comparison: Luxon's `Interval.splitBy` computes each boundary from the start the same way.
+ *   the month's last day (TC39 Temporal `add`, `overflow: "constrain"`), and stepping from that
+ *   boundary would keep the shortened day (February 29, then March 29).
  * - A step that resolves to the same date as the previous boundary is skipped, so no empty
  *   slice is produced. A step that goes backwards returns `[]`.
  * - Returns `[{ start, end }]` when `start === end` (zero-length interval).

package/dist/plain/interval/splitIntervalByUnitDate.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { formatDateInCalendar, NANOSECONDS_PER_DAY_NUMBER, parseCalendarDatePairForArithmetic, plainDateAdd, resolveDurationUnit, tileByUnit, } from "../../internal/index.js";
 import { isValidCalendarDate, isValidDateDurationUnit } from "../validate/index.js";
 import { exceedsPieceLimit, resolveMaxPieces } from "../../internal/maxPieces.js";
@@ -16,9 +16,8 @@ import { minSlicesForSpan } from "../../internal/splitStep.js";
  * - Each boundary is computed from `start` (`start + k × amount`), not by stepping from the
  *   previous boundary, so month-end starts don't drift: a monthly split from January 31 lands
  *   on February 29, March 31, April 30. Temporal's `add` constrains a day the month lacks to
- *   the month's last day, and stepping from that boundary would keep the shortened day
- *   (February 29, then March 29).
- * - Comparison: Luxon's `Interval.splitBy` computes each boundary from the start the same way.
+ *   the month's last day (TC39 Temporal `add`, `overflow: "constrain"`), and stepping from that
+ *   boundary would keep the shortened day (February 29, then March 29).
  * - A step that resolves to the same date as the previous boundary is skipped, so no empty
  *   slice is produced. A step that goes backwards returns `[]`.
  * - Returns `[{ start, end }]` when `start === end` (zero-length interval).

package/dist/plain/interval/splitIntervalByUnitDateTime.d.ts

@@ -12,7 +12,8 @@
  *   lands on February 29, March 31, April 30. Temporal's `add` constrains a day the month lacks
  *   to the month's last day, and stepping from that boundary would keep the shortened day
  *   (February 29, then March 29).
- * - Comparison: Luxon's `Interval.splitBy` computes each boundary from the start the same way.
+ * - Each calendar-unit boundary is `start.add(amount × k)` with Temporal's
+ *   `overflow: "constrain"` (TC39 Temporal `add`), never a step from the previous boundary.
  * - Exact-unit boundaries (hours and smaller) step from the previous boundary. Exact units never
  *   clamp, and stepping keeps nanosecond precision where `k × amount` would pass
  *   `Number.MAX_SAFE_INTEGER`.

package/dist/plain/interval/splitIntervalByUnitDateTime.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDateTime, isValidDateTimeDurationUnit } from "../validate/index.js";
 import { resolveDurationUnit, tileByUnit } from "../../internal/index.js";
 import { exceedsPieceLimit, resolveMaxPieces } from "../../internal/maxPieces.js";
@@ -18,7 +18,8 @@ import { minSlicesForSpan } from "../../internal/splitStep.js";
  *   lands on February 29, March 31, April 30. Temporal's `add` constrains a day the month lacks
  *   to the month's last day, and stepping from that boundary would keep the shortened day
  *   (February 29, then March 29).
- * - Comparison: Luxon's `Interval.splitBy` computes each boundary from the start the same way.
+ * - Each calendar-unit boundary is `start.add(amount × k)` with Temporal's
+ *   `overflow: "constrain"` (TC39 Temporal `add`), never a step from the previous boundary.
  * - Exact-unit boundaries (hours and smaller) step from the previous boundary. Exact units never
  *   clamp, and stepping keeps nanosecond precision where `k × amount` would pass
  *   `Number.MAX_SAFE_INTEGER`.

package/dist/plain/interval/splitIntervalByUnitTime.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime, isValidTimeDurationUnit } from "../validate/index.js";
 import { resolveDurationUnit } from "../../internal/index.js";
 import { exceedsPieceLimit, resolveMaxPieces } from "../../internal/maxPieces.js";

package/dist/plain/interval/validate/isValidDateInterval.d.ts

@@ -6,7 +6,7 @@
  * - Equal `start === end` is valid.
  * - Invalid input, malformed strings, or leap-second strings return `false`.
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Ordering is
- *   calendar-independent, so `start`/`end` may carry different or no calendar tags (D4).
+ *   calendar-independent, so `start`/`end` may carry different or no calendar tags.
  * - Compatibility: since 1.16.0 calendar strings are RFC 9557 (ISO digits, `[u-ca=<id>]`, canonical
  *   calendar ids); see `isValidCalendarDate`.
  *

package/dist/plain/interval/validate/isValidDateInterval.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../../internal/temporal.js";
 import { parseCalendarDateValue } from "../../../internal/index.js";
 import { isValidCalendarDate } from "../../validate/index.js";
 /**
@@ -9,7 +9,7 @@ import { isValidCalendarDate } from "../../validate/index.js";
  * - Equal `start === end` is valid.
  * - Invalid input, malformed strings, or leap-second strings return `false`.
  * - Accepts RFC 9557 calendar-annotated PlainDate strings — E5 (issue #78). Ordering is
- *   calendar-independent, so `start`/`end` may carry different or no calendar tags (D4).
+ *   calendar-independent, so `start`/`end` may carry different or no calendar tags.
  * - Compatibility: since 1.16.0 calendar strings are RFC 9557 (ISO digits, `[u-ca=<id>]`, canonical
  *   calendar ids); see `isValidCalendarDate`.
  *

package/dist/plain/interval/validate/isValidDateTimeInterval.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../../internal/temporal.js";
 import { isValidDateTime } from "../../validate/index.js";
 /**
  * Return true if `start` and `end` form a valid datetime interval — both parseable as

package/dist/plain/interval/validate/isValidTimeInterval.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../../internal/temporal.js";
 import { isValidTime } from "../../validate/index.js";
 /**
  * Return true if `start` and `end` form a valid time interval — both parseable as

package/dist/plain/locale/getLocaleEraNames.d.ts

@@ -11,22 +11,22 @@ import type { LocaleNameStyle } from "./getLocaleMonthNames.js";
  *   a valid locale, only for invalid input.
  * - **A `-u-ca-` subtag in `locale` is ignored.** Both lookups pass `calendar: "gregory"` in the
  *   options bag, and ECMA-402's `ResolveLocale` ranks an options value above the locale
- *   extension, so ``getLocaleEraNames("en-US-u-ca-buddhist")`` returns the same
- *   `["Before Christ", "Anno Domini"]` as ``getLocaleEraNames("en-US")``. That is deliberate — the function is Gregorian by
+ *   extension, so ``getLocaleEraNames("th-TH-u-ca-buddhist")`` returns the same
+ *   `["ปีก่อนคริสตกาล", "คริสต์ศักราช"]` as ``getLocaleEraNames("th-TH")``. That is deliberate — the function is Gregorian by
  *   contract — but it means the tag is accepted and overridden, not rejected. For another
- *   calendar's names, format a date in it: `formatDate("2024-03-15", "en-US-u-ca-buddhist", { era: "long", year: "numeric" })`.
+ *   calendar's names, format a date in it: `formatDate("2024-03-15", "th-TH-u-ca-buddhist", { era: "long", year: "numeric" })`.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 2-element `[BCE-label, CE-label]` array, or `[]` on invalid input
  *
- * @example getLocaleEraNames("en-US") // ["Before Christ", "Anno Domini"]
+ * @example getLocaleEraNames("en-GB") // ["Before Christ", "Anno Domini"]
  * @example getLocaleEraNames("de-DE", "short") // ["v. Chr.", "n. Chr."]
  * @example getLocaleEraNames("ja-JP", "narrow") // ["BC", "AD"]
- * @example getLocaleEraNames("en-US-u-ca-buddhist") // ["Before Christ", "Anno Domini"] (the -u-ca- subtag is overridden)
+ * @example getLocaleEraNames("th-TH-u-ca-buddhist") // ["ปีก่อนคริสตกาล", "คริสต์ศักราช"] (the -u-ca- subtag is overridden)
  * @example getLocaleEraNames("not-a-locale-!!") // []
  * @example getLocaleEraNames(["fr-FR", "en-US"]) // ["avant Jésus-Christ", "après Jésus-Christ"]
  */

package/dist/plain/locale/getLocaleEraNames.js

@@ -1,3 +1,4 @@
+import { cachedFormatter } from "../../internal/formatterCache.js";
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
 import { resolveRequiredLocale } from "../../internal/resolveLocale.js";
 // Imported from its module, not the `internal` barrel: `internal/patternToken.ts` imports this file.
@@ -14,22 +15,22 @@ import { zonedDateTimeFrom } from "../../internal/zonedWallClock.js";
  *   a valid locale, only for invalid input.
  * - **A `-u-ca-` subtag in `locale` is ignored.** Both lookups pass `calendar: "gregory"` in the
  *   options bag, and ECMA-402's `ResolveLocale` ranks an options value above the locale
- *   extension, so ``getLocaleEraNames("en-US-u-ca-buddhist")`` returns the same
- *   `["Before Christ", "Anno Domini"]` as ``getLocaleEraNames("en-US")``. That is deliberate — the function is Gregorian by
+ *   extension, so ``getLocaleEraNames("th-TH-u-ca-buddhist")`` returns the same
+ *   `["ปีก่อนคริสตกาล", "คริสต์ศักราช"]` as ``getLocaleEraNames("th-TH")``. That is deliberate — the function is Gregorian by
  *   contract — but it means the tag is accepted and overridden, not rejected. For another
- *   calendar's names, format a date in it: `formatDate("2024-03-15", "en-US-u-ca-buddhist", { era: "long", year: "numeric" })`.
+ *   calendar's names, format a date in it: `formatDate("2024-03-15", "th-TH-u-ca-buddhist", { era: "long", year: "numeric" })`.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 2-element `[BCE-label, CE-label]` array, or `[]` on invalid input
  *
- * @example getLocaleEraNames("en-US") // ["Before Christ", "Anno Domini"]
+ * @example getLocaleEraNames("en-GB") // ["Before Christ", "Anno Domini"]
  * @example getLocaleEraNames("de-DE", "short") // ["v. Chr.", "n. Chr."]
  * @example getLocaleEraNames("ja-JP", "narrow") // ["BC", "AD"]
- * @example getLocaleEraNames("en-US-u-ca-buddhist") // ["Before Christ", "Anno Domini"] (the -u-ca- subtag is overridden)
+ * @example getLocaleEraNames("th-TH-u-ca-buddhist") // ["ปีก่อนคริสตกาล", "คริสต์ศักราช"] (the -u-ca- subtag is overridden)
  * @example getLocaleEraNames("not-a-locale-!!") // []
  * @example getLocaleEraNames(["fr-FR", "en-US"]) // ["avant Jésus-Christ", "après Jésus-Christ"]
  */
@@ -40,7 +41,7 @@ export function getLocaleEraNames(locale, style = "long") {
             return [];
         try {
             const resolved = style === "short" || style === "narrow" ? style : "long";
-            const formatter = new Intl.DateTimeFormat(resolvedLocale, {
+            const formatter = cachedFormatter("DateTimeFormat", resolvedLocale, {
                 calendar: "gregory",
                 era: resolved,
                 timeZone: "UTC",

package/dist/plain/locale/getLocaleMeridiems.d.ts

@@ -1,19 +1,19 @@
 /**
  * Return a locale's AM/PM (day-period) labels as `[AM-label, PM-label]`.
  *
- * - Labels are locale-varying: `en-US` → `["AM", "PM"]`, `en-GB` →
- *   `["am", "pm"]`, `sv-SE` → `["fm", "em"]`, `zh-CN` → `["上午", "下午"]`,
- *   `ar-SA` → `["ص", "م"]`.
+ * - Labels are locale-varying: `en-GB` → `["am", "pm"]`, `zh-CN` →
+ *   `["上午", "下午"]`, `ar-SA` → `["ص", "م"]`, `sv-SE` → `["fm", "em"]`,
+ *   `en-US` → `["AM", "PM"]`.
  * - Uses the host runtime's `Intl` data via `Intl.DateTimeFormat`, so output
  *   depends on the runtime's ICU build.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @returns 2-element `[AM-label, PM-label]` array, or `[]` on invalid input
  *
- * @example getLocaleMeridiems("en-US") // ["AM", "PM"]
+ * @example getLocaleMeridiems("ar-EG") // ["ص", "م"]
  * @example getLocaleMeridiems("en-GB") // ["am", "pm"]
  * @example getLocaleMeridiems("zh-CN") // ["上午", "下午"]
  * @example getLocaleMeridiems("not-a-locale-!!") // []

package/dist/plain/locale/getLocaleMeridiems.js

@@ -1,20 +1,21 @@
+import { cachedFormatter } from "../../internal/formatterCache.js";
 import { resolveRequiredLocale } from "../../internal/resolveLocale.js";
 /**
  * Return a locale's AM/PM (day-period) labels as `[AM-label, PM-label]`.
  *
- * - Labels are locale-varying: `en-US` → `["AM", "PM"]`, `en-GB` →
- *   `["am", "pm"]`, `sv-SE` → `["fm", "em"]`, `zh-CN` → `["上午", "下午"]`,
- *   `ar-SA` → `["ص", "م"]`.
+ * - Labels are locale-varying: `en-GB` → `["am", "pm"]`, `zh-CN` →
+ *   `["上午", "下午"]`, `ar-SA` → `["ص", "م"]`, `sv-SE` → `["fm", "em"]`,
+ *   `en-US` → `["AM", "PM"]`.
  * - Uses the host runtime's `Intl` data via `Intl.DateTimeFormat`, so output
  *   depends on the runtime's ICU build.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @returns 2-element `[AM-label, PM-label]` array, or `[]` on invalid input
  *
- * @example getLocaleMeridiems("en-US") // ["AM", "PM"]
+ * @example getLocaleMeridiems("ar-EG") // ["ص", "م"]
  * @example getLocaleMeridiems("en-GB") // ["am", "pm"]
  * @example getLocaleMeridiems("zh-CN") // ["上午", "下午"]
  * @example getLocaleMeridiems("not-a-locale-!!") // []
@@ -26,7 +27,7 @@ export function getLocaleMeridiems(locale) {
         if (resolvedLocale === null)
             return [];
         try {
-            const formatter = new Intl.DateTimeFormat(resolvedLocale, {
+            const formatter = cachedFormatter("DateTimeFormat", resolvedLocale, {
                 timeZone: "UTC",
                 hour: "numeric",
                 hour12: true,

package/dist/plain/locale/getLocaleMonthNames.d.ts

@@ -16,22 +16,22 @@ export type LocaleNameStyle = "long" | "short" | "narrow";
  *   are out of scope for this function.
  * - **A `-u-ca-` subtag in `locale` is ignored.** Both lookups pass `calendar: "gregory"` in the
  *   options bag, and ECMA-402's `ResolveLocale` ranks an options value above the locale
- *   extension, so ``getLocaleMonthNames("en-US-u-ca-hebrew")`` returns the same
- *   twelve Gregorian month names as ``getLocaleMonthNames("en-US")``. That is deliberate — the function is Gregorian by
+ *   extension, so ``getLocaleMonthNames("hi-IN-u-ca-indian")`` returns the same
+ *   twelve Gregorian month names as ``getLocaleMonthNames("hi-IN")``. That is deliberate — the function is Gregorian by
  *   contract — but it means the tag is accepted and overridden, not rejected. For another
- *   calendar's names, format a date in it: `formatDate("2024-03-15", "en-US-u-ca-hebrew", { month: "long" })`.
+ *   calendar's names, format a date in it: `formatDate("2024-03-15", "hi-IN-u-ca-indian", { month: "long" })`.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 12-element array of month names in calendar order, or `[]` on invalid input
  *
- * @example getLocaleMonthNames("en-US") // ["January", "February", ... "December"]
+ * @example getLocaleMonthNames("ja-JP") // ["1月", "2月", ... "12月"]
  * @example getLocaleMonthNames("de-DE", "short") // ["Jan", "Feb", "Mär", ... "Dez"]
  * @example getLocaleMonthNames("fr-FR", "narrow") // ["J", "F", "M", ... "D"]
- * @example getLocaleMonthNames("en-US-u-ca-hebrew") // ["January", "February", ... "December"] (the -u-ca- subtag is overridden)
+ * @example getLocaleMonthNames("hi-IN-u-ca-indian") // ["जनवरी", "फ़रवरी", ... "दिसंबर"] (the -u-ca- subtag is overridden)
  * @example getLocaleMonthNames("not-a-locale-!!") // []
  * @example getLocaleMonthNames(["fr-FR", "en-US"]) // ["janvier", "février", …, "décembre"]
  */

package/dist/plain/locale/getLocaleMonthNames.js

@@ -1,6 +1,7 @@
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
+import { cachedFormatter } from "../../internal/formatterCache.js";
 import { resolveRequiredLocale } from "../../internal/resolveLocale.js";
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 /**
  * Return the 12 Gregorian calendar-month names for a locale, in calendar
  * order (January first, December last — not alphabetical).
@@ -12,22 +13,22 @@ import { Temporal } from "@js-temporal/polyfill";
  *   are out of scope for this function.
  * - **A `-u-ca-` subtag in `locale` is ignored.** Both lookups pass `calendar: "gregory"` in the
  *   options bag, and ECMA-402's `ResolveLocale` ranks an options value above the locale
- *   extension, so ``getLocaleMonthNames("en-US-u-ca-hebrew")`` returns the same
- *   twelve Gregorian month names as ``getLocaleMonthNames("en-US")``. That is deliberate — the function is Gregorian by
+ *   extension, so ``getLocaleMonthNames("hi-IN-u-ca-indian")`` returns the same
+ *   twelve Gregorian month names as ``getLocaleMonthNames("hi-IN")``. That is deliberate — the function is Gregorian by
  *   contract — but it means the tag is accepted and overridden, not rejected. For another
- *   calendar's names, format a date in it: `formatDate("2024-03-15", "en-US-u-ca-hebrew", { month: "long" })`.
+ *   calendar's names, format a date in it: `formatDate("2024-03-15", "hi-IN-u-ca-indian", { month: "long" })`.
  * - Returns `[]` if `locale` is not a well-formed BCP 47 tag (ECMA-402 `IsWellFormedLanguageTag`).
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 12-element array of month names in calendar order, or `[]` on invalid input
  *
- * @example getLocaleMonthNames("en-US") // ["January", "February", ... "December"]
+ * @example getLocaleMonthNames("ja-JP") // ["1月", "2月", ... "12月"]
  * @example getLocaleMonthNames("de-DE", "short") // ["Jan", "Feb", "Mär", ... "Dez"]
  * @example getLocaleMonthNames("fr-FR", "narrow") // ["J", "F", "M", ... "D"]
- * @example getLocaleMonthNames("en-US-u-ca-hebrew") // ["January", "February", ... "December"] (the -u-ca- subtag is overridden)
+ * @example getLocaleMonthNames("hi-IN-u-ca-indian") // ["जनवरी", "फ़रवरी", ... "दिसंबर"] (the -u-ca- subtag is overridden)
  * @example getLocaleMonthNames("not-a-locale-!!") // []
  * @example getLocaleMonthNames(["fr-FR", "en-US"]) // ["janvier", "février", …, "décembre"]
  */
@@ -38,13 +39,18 @@ export function getLocaleMonthNames(locale, style = "long") {
             return [];
         try {
             const resolved = style === "short" || style === "narrow" ? style : "long";
+            // One formatter for the twelve dates. A PlainDate formats its own wall-clock fields
+            // (Temporal `PlainDate.prototype.toLocaleString`); the same date's UTC midnight in a
+            // `timeZone: "UTC"` formatter shows the same fields.
+            const formatter = cachedFormatter("DateTimeFormat", resolvedLocale, {
+                month: resolved,
+                calendar: "gregory",
+                timeZone: "UTC",
+            });
             const names = [];
             for (let month = 1; month <= 12; month++) {
                 const date = Temporal.PlainDate.from(`2024-${String(month).padStart(2, "0")}-15`);
-                names.push(date.toLocaleString(resolvedLocale, {
-                    month: resolved,
-                    calendar: "gregory",
-                }));
+                names.push(formatter.format(date.toZonedDateTime("UTC").epochMilliseconds));
             }
             return names;
         }

package/dist/plain/locale/getLocaleWeekdayNames.d.ts

@@ -3,7 +3,7 @@ import type { LocaleNameStyle } from "./getLocaleMonthNames.js";
  * Return the 7 weekday names for a locale, ordered starting from the
  * locale's first day of the week.
  *
- * - The order is the locale's **first day of the week**, never its weekend. For `en-US` and
+ * - The order is the locale's **first day of the week**, never its weekend. For `pt-BR` and
  *   `ar-SA` the array starts with Sunday, for `fr-FR` with Monday, for `ar-EG` with Saturday —
  *   matching GMT's existing locale-first-day convention in `getLocaleDayOfWeek` /
  *   `getLocaleStartOfWeek`. `ar-SA`'s weekend is Friday and Saturday
@@ -18,11 +18,11 @@ import type { LocaleNameStyle } from "./getLocaleMonthNames.js";
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 7-element array of weekday names from the locale's first day, or `[]` on invalid input
  *
- * @example getLocaleWeekdayNames("en-US") // ["Sunday", "Monday", ... "Saturday"]
+ * @example getLocaleWeekdayNames("pt-BR") // ["domingo", "segunda-feira", ... "sábado"]
  * @example getLocaleWeekdayNames("fr-FR") // ["lundi", "mardi", ... "dimanche"]
  * @example getLocaleWeekdayNames("de-DE", "short") // ["Mo", "Di", "Mi", ... "So"]
  * @example getLocaleWeekdayNames("ar-EG")[0] // "السبت" (Saturday — ar-EG's first day, unlike ar-SA's Sunday)

package/dist/plain/locale/getLocaleWeekdayNames.js

@@ -1,11 +1,12 @@
+import { cachedFormatter } from "../../internal/formatterCache.js";
 import { resolveRequiredLocale } from "../../internal/resolveLocale.js";
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { getLocaleFirstDayOfWeek } from "../../internal/getLocaleFirstDayOfWeek.js";
 /**
  * Return the 7 weekday names for a locale, ordered starting from the
  * locale's first day of the week.
  *
- * - The order is the locale's **first day of the week**, never its weekend. For `en-US` and
+ * - The order is the locale's **first day of the week**, never its weekend. For `pt-BR` and
  *   `ar-SA` the array starts with Sunday, for `fr-FR` with Monday, for `ar-EG` with Saturday —
  *   matching GMT's existing locale-first-day convention in `getLocaleDayOfWeek` /
  *   `getLocaleStartOfWeek`. `ar-SA`'s weekend is Friday and Saturday
@@ -20,11 +21,11 @@ import { getLocaleFirstDayOfWeek } from "../../internal/getLocaleFirstDayOfWeek.
  *   A well-formed tag with no matching locale data is not an error: it falls back to the host's
  *   default locale, as ECMA-402 `ResolveLocale` requires.
  *
- * @param locale BCP 47 locale tag (e.g. "en-US", "fr-FR", "ar-SA"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
+ * @param locale BCP 47 locale tag (e.g. "fr-FR", "ar-SA", "en-US"), or a preference list of tags (ECMA-402; the first with locale data is read). Required: omitted, or an empty list (which ECMA-402 would resolve to the host default), returns []
  * @param style Optional name style: `"long"` (default), `"short"`, or `"narrow"`
  * @returns 7-element array of weekday names from the locale's first day, or `[]` on invalid input
  *
- * @example getLocaleWeekdayNames("en-US") // ["Sunday", "Monday", ... "Saturday"]
+ * @example getLocaleWeekdayNames("pt-BR") // ["domingo", "segunda-feira", ... "sábado"]
  * @example getLocaleWeekdayNames("fr-FR") // ["lundi", "mardi", ... "dimanche"]
  * @example getLocaleWeekdayNames("de-DE", "short") // ["Mo", "Di", "Mi", ... "So"]
  * @example getLocaleWeekdayNames("ar-EG")[0] // "السبت" (Saturday — ar-EG's first day, unlike ar-SA's Sunday)
@@ -43,12 +44,18 @@ export function getLocaleWeekdayNames(locale, style = "long") {
             const resolved = style === "short" || style === "narrow" ? style : "long";
             // Build the names in ISO order (Monday-first), then rotate so the
             // locale's first day of week sits at index 0.
+            // One formatter for the seven dates: a PlainDate formats its own wall-clock fields, and
+            // the same date's UTC midnight in a `timeZone: "UTC"` formatter shows the same fields.
+            const formatter = cachedFormatter("DateTimeFormat", resolvedLocale, {
+                weekday: resolved,
+                timeZone: "UTC",
+            });
             const isoOrder = [];
             for (let dayOfWeek = 1; dayOfWeek <= 7; dayOfWeek++) {
                 const date = Temporal.PlainDate.from("2024-01-15").add({
                     days: dayOfWeek - 1,
                 });
-                isoOrder.push(date.toLocaleString(resolvedLocale, { weekday: resolved }));
+                isoOrder.push(formatter.format(date.toZonedDateTime("UTC").epochMilliseconds));
             }
             return isoOrder
                 .slice(firstDay - 1)

package/dist/plain/map/mapDatesInRange.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDate } from "../validate/index.js";
 import { exceedsPieceLimit, resolveMaxPieces } from "../../internal/maxPieces.js";
 /**

package/dist/plain/map/mapDaysInMonth.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 /**
  * Return an array of ISO PlainDate strings for every day in the given year-month.
  *

package/dist/plain/parse/parseDateTimeWithPattern.d.ts

@@ -1,7 +1,7 @@
 import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
 /**
  * Parse a datetime string against a caller-supplied token pattern (e.g.
- * `"MM/dd/yyyy HH:mm:ss"`, `"dd-MMM-yyyy h:mm a"`) and return it as an
+ * `"dd/MM/yyyy HH:mm:ss"`, `"dd-MMM-yyyy h:mm a"`) and return it as an
  * ISO `PlainDateTime` string.
  *
  * - **Decoding, not display.** This is for consuming a *known, fixed*
@@ -48,9 +48,10 @@ import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
  *   (`""`). Any other character that is not a letter (`/ - , space :`,
  *   digits and so on) is a literal with no quoting.
  * - `MMMM`/`MMM`/`EEEE`/`EEE`/`a`/`GGGG`/`GG` are locale-aware. If
- *   `locale` is omitted and the pattern uses any of them, GMT defaults
- *   to `"en-US"` rather than returning `""` for every caller who didn't
- *   have another locale in mind.
+ *   `locale` is omitted (or an empty list) and the pattern uses any of
+ *   them, GMT reads English names in `"en"`, the language with no
+ *   region, rather than returning `""`. CLDR gives `"en"` the same names
+ *   as `"en-US"`. Pass `locale` for any other language.
  * - `EEEE`/`EEE` are matched against the locale's weekday names but the
  *   result is **not** cross-checked against the constructed date — e.g.
  *   `"Monday, 2024-03-15 14:00"` parses successfully against
@@ -63,7 +64,7 @@ import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
  *   pattern is still valid but the hour stays ambiguous — GMT resolves
  *   it as if AM had matched (12 → 0, otherwise unchanged).
  * - Adjacent variable-width numeric tokens with no literal separator
- *   (e.g. `"Mdyyyy"`) are inherently ambiguous: each becomes a greedy
+ *   (e.g. `"dMyyyy"`) are inherently ambiguous: each becomes a greedy
  *   `\d{1,2}`/etc. in sequence, so the split between fields depends on
  *   regex backtracking, not on any documented rule. Prefer zero-padded
  *   tokens (`MM`, `dd`) or an explicit separator for reliable parsing.
@@ -82,21 +83,21 @@ import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
  *   window reads no clock for it. A two-digit year is a legacy form; a
  *   four-digit year is the one to ask a data source for.
  *
- * @param value The string to decode (e.g. "03/15/2024 14:30:00")
- * @param pattern The token pattern describing `value`'s shape (e.g. "MM/dd/yyyy HH:mm:ss")
- * @param locale Optional BCP 47 locale tag, or a preference list of tags, for name-based tokens (default "en-US")
+ * @param value The string to decode (e.g. "15/03/2024 14:30:00")
+ * @param pattern The token pattern describing `value`'s shape (e.g. "dd/MM/yyyy HH:mm:ss")
+ * @param locale Optional BCP 47 locale tag, or a preference list of tags, for name-based tokens (default "en")
  * @param options The hundred-year window a `yy` token resolves in
  * @returns ISO `PlainDateTime` string, or "" on no match, malformed pattern, or invalid input
  *
- * @example parseDateTimeWithPattern("03/15/2024 14:30:00", "MM/dd/yyyy HH:mm:ss") // "2024-03-15T14:30:00"
+ * @example parseDateTimeWithPattern("15/03/2024 14:30:00", "dd/MM/yyyy HH:mm:ss") // "2024-03-15T14:30:00"
  * @example parseDateTimeWithPattern("15-Mar-2024 02:30 PM", "dd-MMM-yyyy hh:mm a") // "2024-03-15T14:30:00"
- * @example parseDateTimeWithPattern("Mar 15, '24 at 14:30", "MMM d, ''yy 'at' HH:mm", undefined, { yearWindow: 2000 }) // "2024-03-15T14:30:00" ('' is one literal quote)
+ * @example parseDateTimeWithPattern("15 Mar '24 at 14:30", "d MMM ''yy 'at' HH:mm", undefined, { yearWindow: 2000 }) // "2024-03-15T14:30:00" ('' is one literal quote)
  * @example parseDateTimeWithPattern("99-03-15 14:30", "yy-MM-dd HH:mm", undefined, { yearWindow: 1950 }) // "1999-03-15T14:30:00" (1950–2049 window)
  * @example parseDateTimeWithPattern("24-03-15 14:30", "yy-MM-dd HH:mm", undefined, { yearWindow: "rolling" }) // "2024-03-15T14:30:00" (while the current UTC year is 1975–2074)
  * @example parseDateTimeWithPattern("24-03-15 14:30", "yy-MM-dd HH:mm") // "" (yy with no window)
- * @example parseDateTimeWithPattern("03/15/2024 14:30:00", "MM/dd/yyyy HH:mm:ss", undefined, { yearWindow: 2000 }) // "2024-03-15T14:30:00" (yyyy ignores the window)
- * @example parseDateTimeWithPattern("02/31/2024 14:30:00", "MM/dd/yyyy HH:mm:ss") // "" (shape-valid, not a real date)
- * @example parseDateTimeWithPattern("not a date", "MM/dd/yyyy HH:mm:ss") // ""
+ * @example parseDateTimeWithPattern("03/15/2024 14:30:00", "MM/dd/yyyy HH:mm:ss", undefined, { yearWindow: 2000 }) // "2024-03-15T14:30:00" (US order; yyyy ignores the window)
+ * @example parseDateTimeWithPattern("31/02/2024 14:30:00", "dd/MM/yyyy HH:mm:ss") // "" (shape-valid, not a real date)
+ * @example parseDateTimeWithPattern("not a date", "dd/MM/yyyy HH:mm:ss") // ""
  * @example parseDateTimeWithPattern("19 mai 2024 10:20", "d MMMM yyyy HH:mm", ["fr-FR", "en-US"]) // "2024-05-19T10:20:00"
  */
 export declare function parseDateTimeWithPattern(value: string, pattern: string, locale?: string | string[], options?: TwoDigitYearOptions): string;