@northguild/gmt 1.18.0 → 1.20.0

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/index.d.ts

@@ -18,7 +18,7 @@ export * from "./parseNanosecondFromDateTime.js";
 export * from "./parseNanosecondFromTime.js";
 export * from "./parseSecondFromDateTime.js";
 export * from "./parseSecondFromTime.js";
-export * from "./parseSql.js";
+export * from "./parseSqlDateTime.js";
 export * from "./parseTimeWithPattern.js";
 export * from "./parseUnitFromDate.js";
 export * from "./parseUnitFromDateTime.js";

package/dist/plain/parse/index.js

@@ -18,7 +18,7 @@ export * from "./parseNanosecondFromDateTime.js";
 export * from "./parseNanosecondFromTime.js";
 export * from "./parseSecondFromDateTime.js";
 export * from "./parseSecondFromTime.js";
-export * from "./parseSql.js";
+export * from "./parseSqlDateTime.js";
 export * from "./parseTimeWithPattern.js";
 export * from "./parseUnitFromDate.js";
 export * from "./parseUnitFromDateTime.js";

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

@@ -1,6 +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*
@@ -17,7 +18,7 @@
  * | Token | Field | Width | Range | Notes |
  * |---|---|---|---|---|
  * | `yyyy` | year | 4 digits | 0000–9999 | |
- * | `yy` | year | 2 digits | 00–99 | Pivot: 00–68 → 2000–2068, 69–99 → 1969–1999 (fixed rule) |
+ * | `yy` | year | 2 digits | 00–99 | Needs `options.yearWindow`; returns `""` without it |
  * | `MM` | month | 2 digits | 01–12 | |
  * | `M` | month | 1-2 digits | 1–12 | |
  * | `MMMM` | month name (long) | locale | — | `getLocaleMonthNames(locale, "long")` |
@@ -47,9 +48,10 @@
  *   (`""`). 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
@@ -62,7 +64,7 @@
  *   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.
@@ -73,17 +75,29 @@
  * - Fields absent from `pattern` default the way `Temporal.PlainDateTime.from`
  *   defaults an omitted field (time fields default to `0`; `year`/`month`/`day`
  *   are still required for a valid result).
+ * - A `yy` token needs the caller's hundred-year window,
+ *   `options.yearWindow`: no standard says which century a two-digit
+ *   year belongs to, and a cut-off built into a library is right today
+ *   and wrong later. Without a valid window a `yy` pattern returns `""`.
+ *   A pattern with no `yy` never reads the option, so a `"rolling"`
+ *   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") // "2024-03-15T14:30:00" ('' is one literal quote)
- * @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("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" (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[]): string;
+export declare function parseDateTimeWithPattern(value: string, pattern: string, locale?: string | string[], options?: TwoDigitYearOptions): string;

package/dist/plain/parse/parseDateTimeWithPattern.js

@@ -1,8 +1,9 @@
-import { Temporal } from "@js-temporal/polyfill";
-import { DATE_TIME_PATTERN_FIELDS, parseValueWithPattern, } from "../../internal/index.js";
+// fallow-ignore-file code-duplication -- sibling of parseDateWithPattern; each keeps its own guard, options check and try/catch, by design
+import { Temporal } from "../../internal/temporal.js";
+import { DATE_TIME_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } from "../../internal/index.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*
@@ -19,7 +20,7 @@ import { DATE_TIME_PATTERN_FIELDS, parseValueWithPattern, } from "../../internal
  * | Token | Field | Width | Range | Notes |
  * |---|---|---|---|---|
  * | `yyyy` | year | 4 digits | 0000–9999 | |
- * | `yy` | year | 2 digits | 00–99 | Pivot: 00–68 → 2000–2068, 69–99 → 1969–1999 (fixed rule) |
+ * | `yy` | year | 2 digits | 00–99 | Needs `options.yearWindow`; returns `""` without it |
  * | `MM` | month | 2 digits | 01–12 | |
  * | `M` | month | 1-2 digits | 1–12 | |
  * | `MMMM` | month name (long) | locale | — | `getLocaleMonthNames(locale, "long")` |
@@ -49,9 +50,10 @@ import { DATE_TIME_PATTERN_FIELDS, parseValueWithPattern, } from "../../internal
  *   (`""`). 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
@@ -64,7 +66,7 @@ import { DATE_TIME_PATTERN_FIELDS, parseValueWithPattern, } from "../../internal
  *   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.
@@ -75,26 +77,40 @@ import { DATE_TIME_PATTERN_FIELDS, parseValueWithPattern, } from "../../internal
  * - Fields absent from `pattern` default the way `Temporal.PlainDateTime.from`
  *   defaults an omitted field (time fields default to `0`; `year`/`month`/`day`
  *   are still required for a valid result).
+ * - A `yy` token needs the caller's hundred-year window,
+ *   `options.yearWindow`: no standard says which century a two-digit
+ *   year belongs to, and a cut-off built into a library is right today
+ *   and wrong later. Without a valid window a `yy` pattern returns `""`.
+ *   A pattern with no `yy` never reads the option, so a `"rolling"`
+ *   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") // "2024-03-15T14:30:00" ('' is one literal quote)
- * @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("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" (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 function parseDateTimeWithPattern(value, pattern, locale) {
+export function parseDateTimeWithPattern(value, pattern, locale, options) {
     try {
         if (typeof value !== "string")
             return "";
         if (typeof pattern !== "string")
             return "";
-        const fields = parseValueWithPattern(value, pattern, locale, DATE_TIME_PATTERN_FIELDS);
+        if (!isOptionsArgument(options))
+            return "";
+        const fields = parseValueWithPattern(value, pattern, locale, DATE_TIME_PATTERN_FIELDS, options);
         if (fields === null)
             return "";
         try {

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

@@ -1,6 +1,7 @@
+import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
 /**
  * Parse a date string against a caller-supplied token pattern (e.g.
- * `"MM/dd/yyyy"`, `"dd-MMM-yyyy"`) and return it as an ISO `PlainDate`
+ * `"dd/MM/yyyy"`, `"dd-MMM-yyyy"`) and return it as an ISO `PlainDate`
  * string.
  *
  * - **Decoding, not display.** This is for consuming a *known, fixed*
@@ -17,7 +18,7 @@
  * | Token | Field | Width | Range | Notes |
  * |---|---|---|---|---|
  * | `yyyy` | year | 4 digits | 0000–9999 | |
- * | `yy` | year | 2 digits | 00–99 | Pivot: 00–68 → 2000–2068, 69–99 → 1969–1999 (fixed rule) |
+ * | `yy` | year | 2 digits | 00–99 | Needs `options.yearWindow`; returns `""` without it |
  * | `MM` | month | 2 digits | 01–12 | |
  * | `M` | month | 1-2 digits | 1–12 | |
  * | `MMMM` | month name (long) | locale | — | `getLocaleMonthNames(locale, "long")` |
@@ -37,9 +38,10 @@
  *   (`""`). Any other character that is not a letter (`/ - , space`,
  *   digits and so on) is a literal with no quoting.
  * - `MMMM`/`MMM`/`EEEE`/`EEE`/`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 — pass `locale` explicitly for others.
+ *   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"` parses successfully against
@@ -47,26 +49,39 @@
  *   This is a deliberate scope limit (no second weekday-index-to-ISO-
  *   dayOfWeek mapping layer).
  * - 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.
  * - A shape-valid match does not by itself prove a real date: extracted
  *   fields are always handed to `Temporal.PlainDate.from(fields, {
- *   overflow: "reject" })`, so `"02/31/2024"` against `"MM/dd/yyyy"`
+ *   overflow: "reject" })`, so `"31/02/2024"` against `"dd/MM/yyyy"`
  *   still returns `""` — the regex only proves the shape, Temporal
  *   proves the date is real.
+ * - A `yy` token needs the caller's hundred-year window,
+ *   `options.yearWindow`: no standard says which century a two-digit
+ *   year belongs to, and a cut-off built into a library is right today
+ *   and wrong later. Without a valid window a `yy` pattern returns `""`.
+ *   A pattern with no `yy` never reads the option, so a `"rolling"`
+ *   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")
- * @param pattern The token pattern describing `value`'s shape (e.g. "MM/dd/yyyy")
- * @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")
+ * @param pattern The token pattern describing `value`'s shape (e.g. "dd/MM/yyyy")
+ * @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 `PlainDate` string, or "" on no match, malformed pattern, or invalid input
  *
- * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy") // "2024-03-15"
+ * @example parseDateWithPattern("15/03/2024", "dd/MM/yyyy") // "2024-03-15"
  * @example parseDateWithPattern("15-Mar-2024", "dd-MMM-yyyy") // "2024-03-15"
- * @example parseDateWithPattern("Mar 15, '24", "MMM d, ''yy") // "2024-03-15" ('' is one literal quote)
- * @example parseDateWithPattern("02/31/2024", "MM/dd/yyyy") // "" (shape-valid, not a real date)
+ * @example parseDateWithPattern("15 Mar '24", "d MMM ''yy", undefined, { yearWindow: 2000 }) // "2024-03-15" ('' is one literal quote)
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy", undefined, { yearWindow: 1950 }) // "2024-03-15" (1950–2049 window)
+ * @example parseDateWithPattern("15.03.99", "dd.MM.yy", undefined, { yearWindow: 1950 }) // "1999-03-15"
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy", undefined, { yearWindow: "rolling" }) // "2024-03-15" (while the current UTC year is 1975–2074)
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy") // "" (yy with no window)
+ * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy", undefined, { yearWindow: 2000 }) // "2024-03-15" (US order; yyyy ignores the window)
+ * @example parseDateWithPattern("31/02/2024", "dd/MM/yyyy") // "" (shape-valid, not a real date)
  * @example parseDateWithPattern("14:30", "HH:mm") // "" (time token in a date-only pattern)
  * @example parseDateWithPattern("19 mai 2024", "d MMMM yyyy", ["fr-FR", "en-US"]) // "2024-05-19"
  */
-export declare function parseDateWithPattern(value: string, pattern: string, locale?: string | string[]): string;
+export declare function parseDateWithPattern(value: string, pattern: string, locale?: string | string[], options?: TwoDigitYearOptions): string;

package/dist/plain/parse/parseDateWithPattern.js

@@ -1,8 +1,9 @@
-import { Temporal } from "@js-temporal/polyfill";
-import { DATE_PATTERN_FIELDS, parseValueWithPattern } from "../../internal/index.js";
+// fallow-ignore-file code-duplication -- sibling of parseDateTimeWithPattern; each keeps its own guard, options check and try/catch, by design
+import { Temporal } from "../../internal/temporal.js";
+import { DATE_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } from "../../internal/index.js";
 /**
  * Parse a date string against a caller-supplied token pattern (e.g.
- * `"MM/dd/yyyy"`, `"dd-MMM-yyyy"`) and return it as an ISO `PlainDate`
+ * `"dd/MM/yyyy"`, `"dd-MMM-yyyy"`) and return it as an ISO `PlainDate`
  * string.
  *
  * - **Decoding, not display.** This is for consuming a *known, fixed*
@@ -19,7 +20,7 @@ import { DATE_PATTERN_FIELDS, parseValueWithPattern } from "../../internal/index
  * | Token | Field | Width | Range | Notes |
  * |---|---|---|---|---|
  * | `yyyy` | year | 4 digits | 0000–9999 | |
- * | `yy` | year | 2 digits | 00–99 | Pivot: 00–68 → 2000–2068, 69–99 → 1969–1999 (fixed rule) |
+ * | `yy` | year | 2 digits | 00–99 | Needs `options.yearWindow`; returns `""` without it |
  * | `MM` | month | 2 digits | 01–12 | |
  * | `M` | month | 1-2 digits | 1–12 | |
  * | `MMMM` | month name (long) | locale | — | `getLocaleMonthNames(locale, "long")` |
@@ -39,9 +40,10 @@ import { DATE_PATTERN_FIELDS, parseValueWithPattern } from "../../internal/index
  *   (`""`). Any other character that is not a letter (`/ - , space`,
  *   digits and so on) is a literal with no quoting.
  * - `MMMM`/`MMM`/`EEEE`/`EEE`/`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 — pass `locale` explicitly for others.
+ *   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"` parses successfully against
@@ -49,35 +51,50 @@ import { DATE_PATTERN_FIELDS, parseValueWithPattern } from "../../internal/index
  *   This is a deliberate scope limit (no second weekday-index-to-ISO-
  *   dayOfWeek mapping layer).
  * - 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.
  * - A shape-valid match does not by itself prove a real date: extracted
  *   fields are always handed to `Temporal.PlainDate.from(fields, {
- *   overflow: "reject" })`, so `"02/31/2024"` against `"MM/dd/yyyy"`
+ *   overflow: "reject" })`, so `"31/02/2024"` against `"dd/MM/yyyy"`
  *   still returns `""` — the regex only proves the shape, Temporal
  *   proves the date is real.
+ * - A `yy` token needs the caller's hundred-year window,
+ *   `options.yearWindow`: no standard says which century a two-digit
+ *   year belongs to, and a cut-off built into a library is right today
+ *   and wrong later. Without a valid window a `yy` pattern returns `""`.
+ *   A pattern with no `yy` never reads the option, so a `"rolling"`
+ *   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")
- * @param pattern The token pattern describing `value`'s shape (e.g. "MM/dd/yyyy")
- * @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")
+ * @param pattern The token pattern describing `value`'s shape (e.g. "dd/MM/yyyy")
+ * @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 `PlainDate` string, or "" on no match, malformed pattern, or invalid input
  *
- * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy") // "2024-03-15"
+ * @example parseDateWithPattern("15/03/2024", "dd/MM/yyyy") // "2024-03-15"
  * @example parseDateWithPattern("15-Mar-2024", "dd-MMM-yyyy") // "2024-03-15"
- * @example parseDateWithPattern("Mar 15, '24", "MMM d, ''yy") // "2024-03-15" ('' is one literal quote)
- * @example parseDateWithPattern("02/31/2024", "MM/dd/yyyy") // "" (shape-valid, not a real date)
+ * @example parseDateWithPattern("15 Mar '24", "d MMM ''yy", undefined, { yearWindow: 2000 }) // "2024-03-15" ('' is one literal quote)
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy", undefined, { yearWindow: 1950 }) // "2024-03-15" (1950–2049 window)
+ * @example parseDateWithPattern("15.03.99", "dd.MM.yy", undefined, { yearWindow: 1950 }) // "1999-03-15"
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy", undefined, { yearWindow: "rolling" }) // "2024-03-15" (while the current UTC year is 1975–2074)
+ * @example parseDateWithPattern("15.03.24", "dd.MM.yy") // "" (yy with no window)
+ * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy", undefined, { yearWindow: 2000 }) // "2024-03-15" (US order; yyyy ignores the window)
+ * @example parseDateWithPattern("31/02/2024", "dd/MM/yyyy") // "" (shape-valid, not a real date)
  * @example parseDateWithPattern("14:30", "HH:mm") // "" (time token in a date-only pattern)
  * @example parseDateWithPattern("19 mai 2024", "d MMMM yyyy", ["fr-FR", "en-US"]) // "2024-05-19"
  */
-export function parseDateWithPattern(value, pattern, locale) {
+export function parseDateWithPattern(value, pattern, locale, options) {
     try {
         if (typeof value !== "string")
             return "";
         if (typeof pattern !== "string")
             return "";
-        const fields = parseValueWithPattern(value, pattern, locale, DATE_PATTERN_FIELDS);
+        if (!isOptionsArgument(options))
+            return "";
+        const fields = parseValueWithPattern(value, pattern, locale, DATE_PATTERN_FIELDS, options);
         if (fields === null)
             return "";
         try {

package/dist/plain/parse/parseDayFromDate.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDate } from "../validate/index.js";
 /**
  * Return the day of month (1-31) for a given ISO 8601 date string.

package/dist/plain/parse/parseDayFromDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDateTime } from "../validate/index.js";
 /**
  * Return the day of month (1-31) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseDayOfWeekFromDate.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDate } from "../validate/index.js";
 /**
  * Return the day of week (1-7) for a given ISO 8601 date string.

package/dist/plain/parse/parseDayOfWeekFromDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDateTime } from "../validate/index.js";
 /**
  * Return the day of week (1-7) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseHourFromDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDateTime } from "../validate/index.js";
 /**
  * Return the hour (00-23) for a given ISO 8601 datetime string.