@northguild/gmt 1.19.0 → 1.20.0

package/dist/plain/parse/parseDateTimeWithPattern.js

@@ -1,9 +1,9 @@
 // fallow-ignore-file code-duplication -- sibling of parseDateWithPattern; each keeps its own guard, options check and try/catch, by design
-import { Temporal } from "@js-temporal/polyfill";
+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*
@@ -50,9 +50,10 @@ import { DATE_TIME_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } f
  *   (`""`). 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
@@ -65,7 +66,7 @@ import { DATE_TIME_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } f
  *   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.
@@ -84,21 +85,21 @@ import { DATE_TIME_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } f
  *   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 function parseDateTimeWithPattern(value, pattern, locale, options) {

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

@@ -1,7 +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*
@@ -38,9 +38,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`/`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
@@ -48,13 +49,13 @@ import type { TwoDigitYearOptions } from "../../types/two-digit-year.js";
  *   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,
@@ -65,21 +66,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")
- * @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", undefined, { yearWindow: 2000 }) // "2024-03-15" ('' is one literal quote)
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy", undefined, { yearWindow: 1950 }) // "2024-03-15" (1950–2049 window)
- * @example parseDateWithPattern("03/15/99", "MM/dd/yy", undefined, { yearWindow: 1950 }) // "1999-03-15"
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy", undefined, { yearWindow: "rolling" }) // "2024-03-15" (while the current UTC year is 1975–2074)
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy") // "" (yy with no window)
- * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy", undefined, { yearWindow: 2000 }) // "2024-03-15" (yyyy ignores the window)
- * @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"
  */

package/dist/plain/parse/parseDateWithPattern.js

@@ -1,9 +1,9 @@
 // fallow-ignore-file code-duplication -- sibling of parseDateTimeWithPattern; each keeps its own guard, options check and try/catch, by design
-import { Temporal } from "@js-temporal/polyfill";
+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*
@@ -40,9 +40,10 @@ import { DATE_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } from "
  *   (`""`). 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
@@ -50,13 +51,13 @@ import { DATE_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } from "
  *   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,
@@ -67,21 +68,21 @@ import { DATE_PATTERN_FIELDS, isOptionsArgument, parseValueWithPattern, } from "
  *   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", undefined, { yearWindow: 2000 }) // "2024-03-15" ('' is one literal quote)
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy", undefined, { yearWindow: 1950 }) // "2024-03-15" (1950–2049 window)
- * @example parseDateWithPattern("03/15/99", "MM/dd/yy", undefined, { yearWindow: 1950 }) // "1999-03-15"
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy", undefined, { yearWindow: "rolling" }) // "2024-03-15" (while the current UTC year is 1975–2074)
- * @example parseDateWithPattern("03/15/24", "MM/dd/yy") // "" (yy with no window)
- * @example parseDateWithPattern("03/15/2024", "MM/dd/yyyy", undefined, { yearWindow: 2000 }) // "2024-03-15" (yyyy ignores the window)
- * @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"
  */

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.

package/dist/plain/parse/parseHourFromTime.js

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

package/dist/plain/parse/parseMicrosecondFromDateTime.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 microsecond (0-999) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseMicrosecondFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime } from "../validate/index.js";
 /**
  * Return the microsecond (0-999) for a given ISO 8601 time string.

package/dist/plain/parse/parseMillisecondFromDateTime.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 millisecond (0-999) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseMillisecondFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime } from "../validate/index.js";
 /**
  * Return the millisecond (0-999) for a given ISO 8601 time string.

package/dist/plain/parse/parseMinuteFromDateTime.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 minute (0-59) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseMinuteFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime } from "../validate/index.js";
 /**
  * Return the minute (0-59) for a given ISO 8601 time string.

package/dist/plain/parse/parseMonthFromDate.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 month (1-12) for a given ISO 8601 date string.

package/dist/plain/parse/parseMonthFromDateTime.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 month (1-12) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseNanosecondFromDateTime.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 nanosecond (0-999) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseNanosecondFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime } from "../validate/index.js";
 /**
  * Return the nanosecond (0-999) for a given ISO 8601 time string.

package/dist/plain/parse/parseSecondFromDateTime.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 second (0-59) for a given ISO 8601 datetime string.

package/dist/plain/parse/parseSecondFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidTime } from "../validate/index.js";
 /**
  * Return the second (0-59) for a given ISO 8601 time string.

package/dist/plain/parse/parseSqlDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { sqlDateTime } from "../../regex/index.js";
 /**
  * Parse a SQL timestamp literal without a time zone — the `YYYY-MM-DD HH:MM:SS[.fff]` form of

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

@@ -33,9 +33,11 @@
  *   `"o'clock"`. A quote that never closes makes the pattern malformed
  *   (`""`). Any other character that is not a letter (`: , space`,
  *   digits and so on) is a literal with no quoting.
- * - `a` is locale-aware. If `locale` is omitted and the pattern uses
- *   `a`, GMT defaults to `"en-US"` rather than returning `""` for every
- *   caller who didn't have another locale in mind.
+ * - `a` is locale-aware. If `locale` is omitted (or an empty list) and
+ *   the pattern uses `a`, GMT reads the English labels in `"en"`, the
+ *   language with no region, rather than returning `""`. CLDR gives
+ *   `"en"` the same AM and PM labels as `"en-US"`. Pass `locale` for any
+ *   other language.
  * - `h`/`hh` resolve to 24-hour using a matched `a` token: if the label
  *   is the PM label and hour !== 12, add 12; if the AM label and hour
  *   === 12, set hour to 0. With no `a` token in the pattern at all, the
@@ -48,7 +50,7 @@
  *
  * @param value The string to decode (e.g. "02:30:45 PM")
  * @param pattern The token pattern describing `value`'s shape (e.g. "hh:mm:ss a")
- * @param locale Optional BCP 47 locale tag, or a preference list of tags, for the meridiem token (default "en-US")
+ * @param locale Optional BCP 47 locale tag, or a preference list of tags, for the meridiem token (default "en")
  * @returns ISO `PlainTime` string, or "" on no match, malformed pattern, or invalid input
  *
  * @example parseTimeWithPattern("14:30:45", "HH:mm:ss") // "14:30:45"

package/dist/plain/parse/parseTimeWithPattern.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { parseValueWithPattern, TIME_PATTERN_FIELDS } from "../../internal/index.js";
 /**
  * Parse a time string against a caller-supplied token pattern (e.g.
@@ -35,9 +35,11 @@ import { parseValueWithPattern, TIME_PATTERN_FIELDS } from "../../internal/index
  *   `"o'clock"`. A quote that never closes makes the pattern malformed
  *   (`""`). Any other character that is not a letter (`: , space`,
  *   digits and so on) is a literal with no quoting.
- * - `a` is locale-aware. If `locale` is omitted and the pattern uses
- *   `a`, GMT defaults to `"en-US"` rather than returning `""` for every
- *   caller who didn't have another locale in mind.
+ * - `a` is locale-aware. If `locale` is omitted (or an empty list) and
+ *   the pattern uses `a`, GMT reads the English labels in `"en"`, the
+ *   language with no region, rather than returning `""`. CLDR gives
+ *   `"en"` the same AM and PM labels as `"en-US"`. Pass `locale` for any
+ *   other language.
  * - `h`/`hh` resolve to 24-hour using a matched `a` token: if the label
  *   is the PM label and hour !== 12, add 12; if the AM label and hour
  *   === 12, set hour to 0. With no `a` token in the pattern at all, the
@@ -50,7 +52,7 @@ import { parseValueWithPattern, TIME_PATTERN_FIELDS } from "../../internal/index
  *
  * @param value The string to decode (e.g. "02:30:45 PM")
  * @param pattern The token pattern describing `value`'s shape (e.g. "hh:mm:ss a")
- * @param locale Optional BCP 47 locale tag, or a preference list of tags, for the meridiem token (default "en-US")
+ * @param locale Optional BCP 47 locale tag, or a preference list of tags, for the meridiem token (default "en")
  * @returns ISO `PlainTime` string, or "" on no match, malformed pattern, or invalid input
  *
  * @example parseTimeWithPattern("14:30:45", "HH:mm:ss") // "14:30:45"

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

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 /**
  * Return a specific date unit extracted from a PlainDate string.
  *

package/dist/plain/parse/parseUnitFromDate.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { resolveDateTimeUnit } from "../../internal/resolveDateTimeUnit.js";
 import { resolveWeekStartsOn } from "../../internal/resolveWeekStartsOn.js";
 import { getWeekNumber } from "../calculate/getWeekNumber.js";

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

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 /**
  * Return a specific unit extracted from a PlainDateTime string.
  *

package/dist/plain/parse/parseUnitFromDateTime.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 { resolveDateTimeUnit } from "../../internal/resolveDateTimeUnit.js";
 import { resolveWeekStartsOn } from "../../internal/resolveWeekStartsOn.js";
 import { getWeekNumber } from "../calculate/getWeekNumber.js";

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

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 /**
  * Return a specific time unit extracted from a PlainTime string.
  *

package/dist/plain/parse/parseUnitFromTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { resolveDateTimeUnit } from "../../internal/resolveDateTimeUnit.js";
 import { isValidTime } from "../validate/index.js";
 /**

package/dist/plain/parse/parseWeekFromDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { resolveWeekStartsOn } from "../../internal/resolveWeekStartsOn.js";
 import { getWeekNumber } from "../calculate/getWeekNumber.js";
 import { isValidDateTime } from "../validate/index.js";

package/dist/plain/parse/parseYearFromDate.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDate } from "../validate/index.js";
 import { isoYearString } from "../../internal/isoYearString.js";
 /**

package/dist/plain/parse/parseYearFromDateTime.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDateTime } from "../validate/index.js";
 import { isoYearString } from "../../internal/isoYearString.js";
 /**

package/dist/plain/validate/{isLeapSecond.d.ts → hasSecond60.d.ts}

@@ -5,7 +5,8 @@
  *   `:59`. It does not check the IERS leap-second list: a real leap second exists only at
  *   23:59:60 UTC at the end of a month in which one was inserted (RFC 3339 §5.7), so
  *   `"2024-12-31T23:59:60Z"` (no leap second that day, IERS Bulletin C 68) and
- *   `"2024-06-15T12:34:60Z"` both return true.
+ *   `"2024-06-15T12:34:60Z"` both return true. It does not check that one was inserted on that
+ *   day; for that, use `isLeapSecond` from `timescale/`.
  * - Matches a seconds field of `60` with any date, time of day or offset, or none, for example
  *   "YYYY-MM-DDT23:59:60Z", "YYYY-MM-DDT23:59:60+00:00", "YYYY-MM-DDT23:59:60" or "23:59:60".
  * - Accepts optional fractional seconds.
@@ -13,22 +14,23 @@
  *   extended or basic digits, a bare time with or without a `T` designator, and a designator,
  *   annotation or nothing after the second. Temporal silently clamps each of them to `:59`, so
  *   each is a leap second GMT has to catch. A `[key=value]` annotation value is never read as a time.
- * - Compatibility: earlier releases recognised only an uppercase `T` with extended digits. To
- *   keep that narrower test, match `/T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/` yourself.
+ * - **Compatibility:** earlier releases of this test (named `isLeapSecond`) recognised only an
+ *   uppercase `T` with extended digits. To keep that narrower test, match
+ *   `/T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/` yourself.
  *
  * @param value ISO date-time or time string
  * @returns true when the string has a second-60 field, otherwise false
  *
- * @example isLeapSecond("2016-12-31T23:59:60Z") // true
- * @example isLeapSecond("2016-12-31T23:59:60.123Z") // true
- * @example isLeapSecond("2016-12-31T23:59:60+00:00") // true
- * @example isLeapSecond("2016-12-31T23:59:60.123+00:00") // true
- * @example isLeapSecond("2016-12-31t23:59:60Z") // true (lowercase t)
- * @example isLeapSecond("20161231 235960Z") // true (space separator, basic format)
- * @example isLeapSecond("2016-12-31T23:59:60") // true (no designator; PlainDateTime clamps it)
- * @example isLeapSecond("23:59:60") // true (a time; PlainTime clamps it)
- * @example isLeapSecond("2016-12-31T23:59:59Z") // false
- * @example isLeapSecond("2024-06-15T12:34:60Z") // true (syntactic: no leap second can occur here)
+ * @example hasSecond60("2016-12-31T23:59:60Z") // true
+ * @example hasSecond60("2016-12-31T23:59:60.123Z") // true
+ * @example hasSecond60("2016-12-31T23:59:60+00:00") // true
+ * @example hasSecond60("2016-12-31T23:59:60.123+00:00") // true
+ * @example hasSecond60("2016-12-31t23:59:60Z") // true (lowercase t)
+ * @example hasSecond60("20161231 235960Z") // true (space separator, basic format)
+ * @example hasSecond60("2016-12-31T23:59:60") // true (no designator; PlainDateTime clamps it)
+ * @example hasSecond60("23:59:60") // true (a time; PlainTime clamps it)
+ * @example hasSecond60("2016-12-31T23:59:59Z") // false
+ * @example hasSecond60("2024-06-15T12:34:60Z") // true (syntactic: no leap second can occur here)
  * @example /T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/.test("2016-12-31t23:59:60Z") // false (the earlier uppercase-T-only test)
  */
-export declare function isLeapSecond(value: string): boolean;
+export declare function hasSecond60(value: string): boolean;

package/dist/plain/validate/{isLeapSecond.js → hasSecond60.js}

@@ -6,7 +6,8 @@ import { leapSecond } from "../../regex/leap-second.js";
  *   `:59`. It does not check the IERS leap-second list: a real leap second exists only at
  *   23:59:60 UTC at the end of a month in which one was inserted (RFC 3339 §5.7), so
  *   `"2024-12-31T23:59:60Z"` (no leap second that day, IERS Bulletin C 68) and
- *   `"2024-06-15T12:34:60Z"` both return true.
+ *   `"2024-06-15T12:34:60Z"` both return true. It does not check that one was inserted on that
+ *   day; for that, use `isLeapSecond` from `timescale/`.
  * - Matches a seconds field of `60` with any date, time of day or offset, or none, for example
  *   "YYYY-MM-DDT23:59:60Z", "YYYY-MM-DDT23:59:60+00:00", "YYYY-MM-DDT23:59:60" or "23:59:60".
  * - Accepts optional fractional seconds.
@@ -14,25 +15,26 @@ import { leapSecond } from "../../regex/leap-second.js";
  *   extended or basic digits, a bare time with or without a `T` designator, and a designator,
  *   annotation or nothing after the second. Temporal silently clamps each of them to `:59`, so
  *   each is a leap second GMT has to catch. A `[key=value]` annotation value is never read as a time.
- * - Compatibility: earlier releases recognised only an uppercase `T` with extended digits. To
- *   keep that narrower test, match `/T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/` yourself.
+ * - **Compatibility:** earlier releases of this test (named `isLeapSecond`) recognised only an
+ *   uppercase `T` with extended digits. To keep that narrower test, match
+ *   `/T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/` yourself.
  *
  * @param value ISO date-time or time string
  * @returns true when the string has a second-60 field, otherwise false
  *
- * @example isLeapSecond("2016-12-31T23:59:60Z") // true
- * @example isLeapSecond("2016-12-31T23:59:60.123Z") // true
- * @example isLeapSecond("2016-12-31T23:59:60+00:00") // true
- * @example isLeapSecond("2016-12-31T23:59:60.123+00:00") // true
- * @example isLeapSecond("2016-12-31t23:59:60Z") // true (lowercase t)
- * @example isLeapSecond("20161231 235960Z") // true (space separator, basic format)
- * @example isLeapSecond("2016-12-31T23:59:60") // true (no designator; PlainDateTime clamps it)
- * @example isLeapSecond("23:59:60") // true (a time; PlainTime clamps it)
- * @example isLeapSecond("2016-12-31T23:59:59Z") // false
- * @example isLeapSecond("2024-06-15T12:34:60Z") // true (syntactic: no leap second can occur here)
+ * @example hasSecond60("2016-12-31T23:59:60Z") // true
+ * @example hasSecond60("2016-12-31T23:59:60.123Z") // true
+ * @example hasSecond60("2016-12-31T23:59:60+00:00") // true
+ * @example hasSecond60("2016-12-31T23:59:60.123+00:00") // true
+ * @example hasSecond60("2016-12-31t23:59:60Z") // true (lowercase t)
+ * @example hasSecond60("20161231 235960Z") // true (space separator, basic format)
+ * @example hasSecond60("2016-12-31T23:59:60") // true (no designator; PlainDateTime clamps it)
+ * @example hasSecond60("23:59:60") // true (a time; PlainTime clamps it)
+ * @example hasSecond60("2016-12-31T23:59:59Z") // false
+ * @example hasSecond60("2024-06-15T12:34:60Z") // true (syntactic: no leap second can occur here)
  * @example /T\d{2}:\d{2}:60(?:[.,]\d+)?[-+Zz[]/.test("2016-12-31t23:59:60Z") // false (the earlier uppercase-T-only test)
  */
-export function isLeapSecond(value) {
+export function hasSecond60(value) {
     if (typeof value !== "string") {
         return false;
     }

package/dist/plain/validate/index.d.ts

@@ -1,4 +1,4 @@
-export * from "./isLeapSecond.js";
+export * from "./hasSecond60.js";
 export * from "./isLeapYear.js";
 export * from "./isValidCalendarDate.js";
 export * from "./isValidDate.js";

package/dist/plain/validate/index.js

@@ -1,4 +1,4 @@
-export * from "./isLeapSecond.js";
+export * from "./hasSecond60.js";
 export * from "./isLeapYear.js";
 export * from "./isValidCalendarDate.js";
 export * from "./isValidDate.js";