@northguild/gmt 1.19.0 → 1.20.0

package/dist/plain/validate/isLeapYear.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidDate } from "./isValidDate.js";
 /**
  * Return true when the given PlainDate falls in a leap year.

package/dist/plain/validate/isValidDate.js

@@ -1,7 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
-import { isoStringBody } from "../../internal/isoStringBody.js";
-import { plainDate } from "../../regex/index.js";
-import { isLeapSecond } from "./isLeapSecond.js";
+import { isDateString } from "../../internal/inputChecks.js";
 /**
  * Return true if `value` is a valid ISO PlainDate string.
  *
@@ -26,17 +23,5 @@ import { isLeapSecond } from "./isLeapSecond.js";
  * @example isValidDate("2024-12-31T23:59:60") // false (leap second - not a valid date)
  */
 export function isValidDate(value) {
-    const body = isoStringBody(value);
-    if (isLeapSecond(body)) {
-        return false;
-    }
-    if (!plainDate.test(body)) {
-        return false;
-    }
-    try {
-        return Temporal.PlainDate.from(value).calendarId === "iso8601";
-    }
-    catch {
-        return false;
-    }
+    return isDateString(value);
 }

package/dist/plain/validate/isValidDateRange.js

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

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

@@ -13,7 +13,7 @@
  *
  * @example isValidDateTime("2024-02-29T12:34:56") // true
  * @example isValidDateTime("2024-02-30T12:34:56") // false (invalid date)
- * @example isValidDateTime("2024-02-29T12:34:56[America/New_York]") // true (time zone annotation ignored)
+ * @example isValidDateTime("2024-02-29T12:34:56[Asia/Kolkata]") // true (time zone annotation ignored)
  * @example isValidDateTime("2024-02-29T12:34:56[!foo=bar]") // false (unknown critical annotation)
  * @example isValidDateTime("2024-02-29T12:34:56[u-ca=hebrew]") // false (non-ISO calendar)
  * @example isValidDateTime("2024-02-29T24:00:00") // false (invalid time)

package/dist/plain/validate/isValidDateTime.js

@@ -1,7 +1,7 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isoStringBody } from "../../internal/isoStringBody.js";
 import { plainDateTime } from "../../regex/index.js";
-import { isLeapSecond } from "./isLeapSecond.js";
+import { hasSecond60 } from "./hasSecond60.js";
 /**
  * Return true when `value` is a valid PlainDateTime string.
  *
@@ -17,7 +17,7 @@ import { isLeapSecond } from "./isLeapSecond.js";
  *
  * @example isValidDateTime("2024-02-29T12:34:56") // true
  * @example isValidDateTime("2024-02-30T12:34:56") // false (invalid date)
- * @example isValidDateTime("2024-02-29T12:34:56[America/New_York]") // true (time zone annotation ignored)
+ * @example isValidDateTime("2024-02-29T12:34:56[Asia/Kolkata]") // true (time zone annotation ignored)
  * @example isValidDateTime("2024-02-29T12:34:56[!foo=bar]") // false (unknown critical annotation)
  * @example isValidDateTime("2024-02-29T12:34:56[u-ca=hebrew]") // false (non-ISO calendar)
  * @example isValidDateTime("2024-02-29T24:00:00") // false (invalid time)
@@ -25,7 +25,7 @@ import { isLeapSecond } from "./isLeapSecond.js";
  */
 export function isValidDateTime(value) {
     const body = isoStringBody(value);
-    if (isLeapSecond(body)) {
+    if (hasSecond60(body)) {
         return false;
     }
     if (!plainDateTime.test(body)) {

package/dist/plain/validate/isValidDateTimeRange.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 } from "./isValidDateTime.js";
 import { isObject, isOptionsArgument } from "../../internal/isObject.js";
 /**

package/dist/plain/validate/isValidIsoDateLike.js

@@ -1,7 +1,7 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isoStringBody } from "../../internal/isoStringBody.js";
 import { plainDate, plainDateTime } from "../../regex/index.js";
-import { isLeapSecond } from "./isLeapSecond.js";
+import { hasSecond60 } from "./hasSecond60.js";
 /**
  * Return true when the input is a valid PlainDate or PlainDateTime ISO string.
  *
@@ -25,7 +25,7 @@ import { isLeapSecond } from "./isLeapSecond.js";
  */
 export function isValidIsoDateLike(value) {
     const body = isoStringBody(value);
-    if (isLeapSecond(body)) {
+    if (hasSecond60(body)) {
         return false;
     }
     if (plainDate.test(body)) {

package/dist/plain/validate/isValidTime.js

@@ -1,7 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
-import { isoStringBody } from "../../internal/isoStringBody.js";
-import { plainTime } from "../../regex/index.js";
-import { isLeapSecond } from "./isLeapSecond.js";
+import { isTimeString } from "../../internal/inputChecks.js";
 /**
  * Return true when `value` is a valid ISO PlainTime string.
  *
@@ -23,18 +20,5 @@ import { isLeapSecond } from "./isLeapSecond.js";
  * @example isValidTime("23:59:60") // false (leap second)
  */
 export function isValidTime(value) {
-    const body = isoStringBody(value);
-    if (isLeapSecond(body)) {
-        return false;
-    }
-    if (!plainTime.test(body)) {
-        return false;
-    }
-    try {
-        Temporal.PlainTime.from(value);
-        return true;
-    }
-    catch {
-        return false;
-    }
+    return isTimeString(value);
 }

package/dist/plain/validate/isValidTimeRange.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 } from "./isValidTime.js";
 import { isObject, isOptionsArgument } from "../../internal/isObject.js";
 /**

package/dist/precision/convert/fromNanoseconds.d.ts

@@ -2,7 +2,7 @@
  * Convert nanoseconds since the Unix epoch back to an ISO 8601 string.
  *
  * - Returns a UTC instant string when no time zone is given, and a zoned string
- *   (`"...[America/New_York]"`) when one is.
+ *   (`"...[Asia/Tokyo]"`) when one is.
  * - No disambiguation policy applies: an instant maps to exactly one wall time in a zone,
  *   so DST gaps and overlaps cannot arise on this direction of the conversion.
  * - A time zone, when given, must be a time zone identifier: an IANA name or a UTC offset to the
@@ -26,7 +26,7 @@
  *
  * @example fromNanoseconds(0n) // "1970-01-01T00:00:00Z"
  * @example fromNanoseconds(1710072000123456789n) // "2024-03-10T12:00:00.123456789Z"
- * @example fromNanoseconds(1710072000123456789n, "America/New_York") // "2024-03-10T08:00:00.123456789-04:00[America/New_York]"
+ * @example fromNanoseconds(1710072000123456789n, "Asia/Tokyo") // "2024-03-10T21:00:00.123456789+09:00[Asia/Tokyo]"
  * @example fromNanoseconds(-1000000000n) // "1969-12-31T23:59:59Z"
  * @example fromNanoseconds(0n, "Not/AZone") // ""
  * @example fromNanoseconds(0n, undefined) // "1970-01-01T00:00:00Z" — undefined is the same as omitted

package/dist/precision/convert/fromNanoseconds.js

@@ -1,11 +1,11 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidEpochNanoseconds } from "../../internal/index.js";
 import { isValidTimeZone } from "../../zoned/validate/index.js";
 /**
  * Convert nanoseconds since the Unix epoch back to an ISO 8601 string.
  *
  * - Returns a UTC instant string when no time zone is given, and a zoned string
- *   (`"...[America/New_York]"`) when one is.
+ *   (`"...[Asia/Tokyo]"`) when one is.
  * - No disambiguation policy applies: an instant maps to exactly one wall time in a zone,
  *   so DST gaps and overlaps cannot arise on this direction of the conversion.
  * - A time zone, when given, must be a time zone identifier: an IANA name or a UTC offset to the
@@ -29,7 +29,7 @@ import { isValidTimeZone } from "../../zoned/validate/index.js";
  *
  * @example fromNanoseconds(0n) // "1970-01-01T00:00:00Z"
  * @example fromNanoseconds(1710072000123456789n) // "2024-03-10T12:00:00.123456789Z"
- * @example fromNanoseconds(1710072000123456789n, "America/New_York") // "2024-03-10T08:00:00.123456789-04:00[America/New_York]"
+ * @example fromNanoseconds(1710072000123456789n, "Asia/Tokyo") // "2024-03-10T21:00:00.123456789+09:00[Asia/Tokyo]"
  * @example fromNanoseconds(-1000000000n) // "1969-12-31T23:59:59Z"
  * @example fromNanoseconds(0n, "Not/AZone") // ""
  * @example fromNanoseconds(0n, undefined) // "1970-01-01T00:00:00Z" — undefined is the same as omitted

package/dist/precision/convert/toNanoseconds.d.ts

@@ -32,8 +32,8 @@
  * @example toNanoseconds("1970-01-01T00:00:00Z") // 0n
  * @example toNanoseconds("2024-03-10T12:00:00.123456789Z") // 1710072000123456789n
  * @example toNanoseconds("1969-12-31T23:59:59Z") // -1000000000n
- * @example toNanoseconds("2024-03-10T12:00:00-05:00[America/New_York]") // 1710090000000000000n
- * @example toNanoseconds("2024-03-10T12:00:00+05:00[America/New_York]") // 1710054000000000000n — the offset decides, the zone is not checked
+ * @example toNanoseconds("2024-03-10T12:00:00+05:30[Asia/Kolkata]") // 1710052200000000000n
+ * @example toNanoseconds("2024-03-10T12:00:00+05:00[Asia/Kolkata]") // 1710054000000000000n — the offset decides, the zone is not checked
  * @example toNanoseconds("1960-01-01T00:20:00-00:45[Africa/Monrovia]") // -315615330000000000n — the zone's −00:44:30, which `-00:45` rounds
  * @example toNanoseconds("2024-03-10T12:00:00") // 0n — no offset designator
  * @example toNanoseconds("20240310T120000Z") // 0n — basic format

package/dist/precision/convert/toNanoseconds.js

@@ -33,8 +33,8 @@ import { parseInstantNanoseconds } from "../../internal/index.js";
  * @example toNanoseconds("1970-01-01T00:00:00Z") // 0n
  * @example toNanoseconds("2024-03-10T12:00:00.123456789Z") // 1710072000123456789n
  * @example toNanoseconds("1969-12-31T23:59:59Z") // -1000000000n
- * @example toNanoseconds("2024-03-10T12:00:00-05:00[America/New_York]") // 1710090000000000000n
- * @example toNanoseconds("2024-03-10T12:00:00+05:00[America/New_York]") // 1710054000000000000n — the offset decides, the zone is not checked
+ * @example toNanoseconds("2024-03-10T12:00:00+05:30[Asia/Kolkata]") // 1710052200000000000n
+ * @example toNanoseconds("2024-03-10T12:00:00+05:00[Asia/Kolkata]") // 1710054000000000000n — the offset decides, the zone is not checked
  * @example toNanoseconds("1960-01-01T00:20:00-00:45[Africa/Monrovia]") // -315615330000000000n — the zone's −00:44:30, which `-00:45` rounds
  * @example toNanoseconds("2024-03-10T12:00:00") // 0n — no offset designator
  * @example toNanoseconds("20240310T120000Z") // 0n — basic format

package/dist/precision/index.d.ts

@@ -1,4 +1,4 @@
-export * from "@js-temporal/polyfill";
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calculate/index.js";
 export * from "./convert/index.js";
 export * from "./format/index.js";

package/dist/precision/index.js

@@ -1,5 +1,5 @@
-// Re-export the Temporal polyfill (`Temporal`, `Intl`, `toTemporalInstant`) so every namespace subpath offers it
-export * from "@js-temporal/polyfill";
+// Re-export `Temporal`, `Intl` and `toTemporalInstant` from the internal seam so every namespace subpath offers them
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calculate/index.js";
 export * from "./convert/index.js";
 export * from "./format/index.js";

package/dist/precision/validate/isValidInstant.d.ts

@@ -35,7 +35,7 @@
  *
  * @example isValidInstant("2024-03-10T12:00:00Z") // true
  * @example isValidInstant("1970-01-01T00:00:00Z") // true — the epoch, where toNanoseconds returns 0n
- * @example isValidInstant("2024-03-10T12:00:00-05:00[America/New_York]") // true
+ * @example isValidInstant("2024-03-10T12:00:00+05:30[Asia/Kolkata]") // true
  * @example isValidInstant("2024-03-10T12:00:00Z[Not/AZone]") // true — the zone annotation is not checked
  * @example isValidInstant("2024-03-10T12:00:00-05:00") // true — isValidUtc says false
  * @example isValidInstant("2024-03-10 12:00:00Z") // false — space separator (extended format only)

package/dist/precision/validate/isValidInstant.js

@@ -36,7 +36,7 @@ import { parseInstantNanoseconds } from "../../internal/index.js";
  *
  * @example isValidInstant("2024-03-10T12:00:00Z") // true
  * @example isValidInstant("1970-01-01T00:00:00Z") // true — the epoch, where toNanoseconds returns 0n
- * @example isValidInstant("2024-03-10T12:00:00-05:00[America/New_York]") // true
+ * @example isValidInstant("2024-03-10T12:00:00+05:30[Asia/Kolkata]") // true
  * @example isValidInstant("2024-03-10T12:00:00Z[Not/AZone]") // true — the zone annotation is not checked
  * @example isValidInstant("2024-03-10T12:00:00-05:00") // true — isValidUtc says false
  * @example isValidInstant("2024-03-10 12:00:00Z") // false — space separator (extended format only)

package/dist/regex/calendar-zoned-date-time.d.ts

@@ -3,13 +3,13 @@
  * and reads — the zoned sibling of `calendarDate` (regex/calendar-date.ts):
  *
  *   <date>T<time><offset>[<timeZone>][u-ca=<id>]
- *   2024-02-24T14:30:00-05:00[America/New_York][u-ca=hebrew]
+ *   2024-02-24T14:30:00+02:00[Asia/Jerusalem][u-ca=hebrew]
  *
  * This is exactly `Temporal.ZonedDateTime#toString()` for a non-ISO calendar. The digits are ISO
  * and the calendar annotation follows the time zone annotation, in RFC 9557 §4.1 order. The date,
  * time and offset are ISO 8601 extended format with an upper-case `Z`. The date
  * half and the annotation are the same groups as `calendarDate`'s. The offset is optional; the
- * time zone annotation may carry RFC 9557's critical flag (`[!America/New_York]`), and so may the
+ * time zone annotation may carry RFC 9557's critical flag (`[!Asia/Jerusalem]`), and so may the
  * calendar annotation.
  *
  * A match proves shape only: `internal/calendarZonedString.ts` hands the string to
@@ -23,8 +23,8 @@
  * Capture groups: 1 year, 2 month, 3 day, 4 time, 5 offset (optional), 6 time zone annotation
  * (with its critical flag, if any), 7 calendar critical flag (`"!"` or undefined), 8 calendar id.
  *
- * @example calendarZonedDateTime.test("2024-02-24T14:30:00-05:00[America/New_York][u-ca=hebrew]") // true
- * @example calendarZonedDateTime.test("2024-02-24T14:30:00-05:00[u-ca=hebrew][America/New_York]") // false (calendar before zone)
+ * @example calendarZonedDateTime.test("2024-02-24T14:30:00+02:00[Asia/Jerusalem][u-ca=hebrew]") // true
+ * @example calendarZonedDateTime.test("2024-02-24T14:30:00+02:00[u-ca=hebrew][Asia/Jerusalem]") // false (calendar before zone)
  * @example calendarZonedDateTime.test("2024-03-15T14:30:00Z[UTC]") // false (no calendar annotation)
  */
 export declare const calendarZonedDateTime: RegExp;

package/dist/regex/calendar-zoned-date-time.js

@@ -3,13 +3,13 @@
  * and reads — the zoned sibling of `calendarDate` (regex/calendar-date.ts):
  *
  *   <date>T<time><offset>[<timeZone>][u-ca=<id>]
- *   2024-02-24T14:30:00-05:00[America/New_York][u-ca=hebrew]
+ *   2024-02-24T14:30:00+02:00[Asia/Jerusalem][u-ca=hebrew]
  *
  * This is exactly `Temporal.ZonedDateTime#toString()` for a non-ISO calendar. The digits are ISO
  * and the calendar annotation follows the time zone annotation, in RFC 9557 §4.1 order. The date,
  * time and offset are ISO 8601 extended format with an upper-case `Z`. The date
  * half and the annotation are the same groups as `calendarDate`'s. The offset is optional; the
- * time zone annotation may carry RFC 9557's critical flag (`[!America/New_York]`), and so may the
+ * time zone annotation may carry RFC 9557's critical flag (`[!Asia/Jerusalem]`), and so may the
  * calendar annotation.
  *
  * A match proves shape only: `internal/calendarZonedString.ts` hands the string to
@@ -23,8 +23,8 @@
  * Capture groups: 1 year, 2 month, 3 day, 4 time, 5 offset (optional), 6 time zone annotation
  * (with its critical flag, if any), 7 calendar critical flag (`"!"` or undefined), 8 calendar id.
  *
- * @example calendarZonedDateTime.test("2024-02-24T14:30:00-05:00[America/New_York][u-ca=hebrew]") // true
- * @example calendarZonedDateTime.test("2024-02-24T14:30:00-05:00[u-ca=hebrew][America/New_York]") // false (calendar before zone)
+ * @example calendarZonedDateTime.test("2024-02-24T14:30:00+02:00[Asia/Jerusalem][u-ca=hebrew]") // true
+ * @example calendarZonedDateTime.test("2024-02-24T14:30:00+02:00[u-ca=hebrew][Asia/Jerusalem]") // false (calendar before zone)
  * @example calendarZonedDateTime.test("2024-03-15T14:30:00Z[UTC]") // false (no calendar annotation)
  */
 export const calendarZonedDateTime = /^(\d{4}|\+\d{6}|-(?!0{6})\d{6})-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])T(\d{2}:\d{2}(?::\d{2}(?:[.,]\d{1,9})?)?)((?:[+-]\d{2}:\d{2}(?::\d{2}(?:[.,]\d{1,9})?)?)|Z)?\[(!?[^[\]=!]+)\]\[(!)?u-ca=([A-Za-z0-9]+(?:-[A-Za-z0-9]+)*)\]$/;

package/dist/regex/index.d.ts

@@ -1,4 +1,4 @@
-export * from "@js-temporal/polyfill";
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calendar-date.js";
 export * from "./calendar-zoned-date-time.js";
 export * from "./date.js";

package/dist/regex/index.js

@@ -1,5 +1,5 @@
-// Re-export the Temporal polyfill (`Temporal`, `Intl`, `toTemporalInstant`) so every namespace subpath offers it
-export * from "@js-temporal/polyfill";
+// Re-export `Temporal`, `Intl` and `toTemporalInstant` from the internal seam so every namespace subpath offers them
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calendar-date.js";
 export * from "./calendar-zoned-date-time.js";
 export * from "./date.js";

package/dist/regex/leap-second.d.ts

@@ -15,7 +15,7 @@
  * - Rejecting a leap second is GMT's decision, not the grammar's range: Temporal's
  *   `TimeSecond` and RFC 3339's `time-second` both admit 60. GMT refuses the value because
  *   Temporal cannot represent it and would otherwise read it as `:59`.
- * - Used by `isLeapSecond`. Validators reject a second of 60 in their own patterns.
+ * - Used by `hasSecond60`. Validators reject a second of 60 in their own patterns.
  *
  * @example leapSecond.test("2024-12-31T23:59:60Z")                // true
  * @example leapSecond.test("2024-12-31T23:59:60.123+00:00")       // true

package/dist/regex/leap-second.js

@@ -15,7 +15,7 @@
  * - Rejecting a leap second is GMT's decision, not the grammar's range: Temporal's
  *   `TimeSecond` and RFC 3339's `time-second` both admit 60. GMT refuses the value because
  *   Temporal cannot represent it and would otherwise read it as `:59`.
- * - Used by `isLeapSecond`. Validators reject a second of 60 in their own patterns.
+ * - Used by `hasSecond60`. Validators reject a second of 60 in their own patterns.
  *
  * @example leapSecond.test("2024-12-31T23:59:60Z")                // true
  * @example leapSecond.test("2024-12-31T23:59:60.123+00:00")       // true

package/dist/regex/time-zone-like.d.ts

@@ -14,12 +14,12 @@
  *   `Etc/GMT+5`). Temporal must accept every Zone and Link name in the IANA database, and tzdb's
  *   `backward` file has more than forty slash-less ones.
  * - Letter case is not checked: ECMA-402 matches an identifier ASCII-case-insensitively, so `utc`
- *   and `america/new_york` name the same zones as `UTC` and `America/New_York`.
+ *   and `asia/kolkata` name the same zones as `UTC` and `Asia/Kolkata`.
  * - SHAPE ONLY. Whether the name exists is decided by Temporal: its only consumer,
  *   `isValidTimeZone`, also requires `Temporal.ZonedDateTime.from` to accept the zone.
  *
  * @example timeZoneLike.test("UTC")              // true
- * @example timeZoneLike.test("America/New_York") // true
+ * @example timeZoneLike.test("Asia/Kolkata")     // true
  * @example timeZoneLike.test("Japan")            // true (single-component IANA link)
  * @example timeZoneLike.test("Etc/GMT+5")        // true
  * @example timeZoneLike.test("Custom/Zone")      // true (shape only; existence is not checked)

package/dist/regex/time-zone-like.js

@@ -14,12 +14,12 @@
  *   `Etc/GMT+5`). Temporal must accept every Zone and Link name in the IANA database, and tzdb's
  *   `backward` file has more than forty slash-less ones.
  * - Letter case is not checked: ECMA-402 matches an identifier ASCII-case-insensitively, so `utc`
- *   and `america/new_york` name the same zones as `UTC` and `America/New_York`.
+ *   and `asia/kolkata` name the same zones as `UTC` and `Asia/Kolkata`.
  * - SHAPE ONLY. Whether the name exists is decided by Temporal: its only consumer,
  *   `isValidTimeZone`, also requires `Temporal.ZonedDateTime.from` to accept the zone.
  *
  * @example timeZoneLike.test("UTC")              // true
- * @example timeZoneLike.test("America/New_York") // true
+ * @example timeZoneLike.test("Asia/Kolkata")     // true
  * @example timeZoneLike.test("Japan")            // true (single-component IANA link)
  * @example timeZoneLike.test("Etc/GMT+5")        // true
  * @example timeZoneLike.test("Custom/Zone")      // true (shape only; existence is not checked)

package/dist/span/calculate/spanMs.d.ts

@@ -39,7 +39,8 @@
  * - Leap seconds are not counted. UTC repeats a second rather than numbering a 61st one, so
  *   a span across one is a second short of the physical elapsed time; against a smeared
  *   clock (Google, AWS, Meta) the error is up to a second spread over the smear window.
- *   Leap-second-exact spans need a TAI scale, which GMT does not yet ship.
+ *   For a leap-second-exact span, convert both ends with `toTAI` or add
+ *   `leapSecondsBetween(start, end)` seconds, both from `timescale/`.
  *
  * @param start ISO 8601 instant string the span is measured from
  * @param end ISO 8601 instant string the span is measured to
@@ -49,8 +50,8 @@
  * @example spanMs("2024-03-10T12:00:01Z", "2024-03-10T12:00:00Z") // -1000
  * @example spanMs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00Z") // 0
  * @example spanMs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00.123456789Z") // 123.456789
- * @example spanMs("2024-03-09T12:00:00-05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 82800000 — 23 hours, not 24
- * @example spanMs("2024-03-10T12:00:00+05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 32400000 — offsets decide, the zone is not checked
+ * @example spanMs("2024-03-30T12:00:00+00:00[Europe/London]", "2024-03-31T12:00:00+01:00[Europe/London]") // 82800000 — 23 hours, not 24
+ * @example spanMs("2024-03-10T12:00:00+05:00[Asia/Tokyo]", "2024-03-10T12:00:00-04:00[Asia/Tokyo]") // 32400000 — offsets decide, the zone is not checked
  * @example spanMs("1960-01-01T01:04:30Z", "1960-01-01T00:20:00-00:45[Africa/Monrovia]") // 0 — the zone's −00:44:30, which `-00:45` rounds
  * @example spanMs("-271821-04-20T00:00:00Z", "+275760-09-13T00:00:00Z") // null — past the safe integer range, use spanNs
  * @example spanMs("2024-03-10T12:00:00Z", "invalid") // null

package/dist/span/calculate/spanMs.js

@@ -51,7 +51,8 @@ const MAX_SAFE_NANOSECONDS = BigInt(Number.MAX_SAFE_INTEGER) * NANOSECONDS_PER_M
  * - Leap seconds are not counted. UTC repeats a second rather than numbering a 61st one, so
  *   a span across one is a second short of the physical elapsed time; against a smeared
  *   clock (Google, AWS, Meta) the error is up to a second spread over the smear window.
- *   Leap-second-exact spans need a TAI scale, which GMT does not yet ship.
+ *   For a leap-second-exact span, convert both ends with `toTAI` or add
+ *   `leapSecondsBetween(start, end)` seconds, both from `timescale/`.
  *
  * @param start ISO 8601 instant string the span is measured from
  * @param end ISO 8601 instant string the span is measured to
@@ -61,8 +62,8 @@ const MAX_SAFE_NANOSECONDS = BigInt(Number.MAX_SAFE_INTEGER) * NANOSECONDS_PER_M
  * @example spanMs("2024-03-10T12:00:01Z", "2024-03-10T12:00:00Z") // -1000
  * @example spanMs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00Z") // 0
  * @example spanMs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00.123456789Z") // 123.456789
- * @example spanMs("2024-03-09T12:00:00-05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 82800000 — 23 hours, not 24
- * @example spanMs("2024-03-10T12:00:00+05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 32400000 — offsets decide, the zone is not checked
+ * @example spanMs("2024-03-30T12:00:00+00:00[Europe/London]", "2024-03-31T12:00:00+01:00[Europe/London]") // 82800000 — 23 hours, not 24
+ * @example spanMs("2024-03-10T12:00:00+05:00[Asia/Tokyo]", "2024-03-10T12:00:00-04:00[Asia/Tokyo]") // 32400000 — offsets decide, the zone is not checked
  * @example spanMs("1960-01-01T01:04:30Z", "1960-01-01T00:20:00-00:45[Africa/Monrovia]") // 0 — the zone's −00:44:30, which `-00:45` rounds
  * @example spanMs("-271821-04-20T00:00:00Z", "+275760-09-13T00:00:00Z") // null — past the safe integer range, use spanNs
  * @example spanMs("2024-03-10T12:00:00Z", "invalid") // null

package/dist/span/calculate/spanNs.d.ts

@@ -31,7 +31,8 @@
  * - Leap seconds are not counted. UTC repeats a second rather than numbering a 61st one, so
  *   a span across one is a second short of the physical elapsed time; against a smeared
  *   clock (Google, AWS, Meta) the error is up to a second spread over the smear window.
- *   Leap-second-exact spans need a TAI scale, which GMT does not yet ship.
+ *   For a leap-second-exact span, convert both ends with `toTAI` or add
+ *   `leapSecondsBetween(start, end)` seconds, both from `timescale/`.
  *
  * @param start ISO 8601 instant string the span is measured from
  * @param end ISO 8601 instant string the span is measured to
@@ -41,8 +42,8 @@
  * @example spanNs("2024-03-10T12:00:01Z", "2024-03-10T12:00:00Z") // -1000000000n
  * @example spanNs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00Z") // 0n
  * @example spanNs("2024-03-10T12:00:00.123456789Z", "2024-03-10T12:00:00.123456790Z") // 1n
- * @example spanNs("2024-03-10T07:00:00-05:00[America/New_York]", "2024-03-10T12:00:00Z") // 0n — same instant, different zones
- * @example spanNs("2024-03-10T12:00:00+05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 32400000000000n — offsets decide, the zone is not checked
+ * @example spanNs("2024-03-10T07:00:00-05:00[America/Bogota]", "2024-03-10T12:00:00Z") // 0n — same instant, different zones
+ * @example spanNs("2024-03-10T12:00:00+05:00[Asia/Tokyo]", "2024-03-10T12:00:00-04:00[Asia/Tokyo]") // 32400000000000n — offsets decide, the zone is not checked
  * @example spanNs("1960-01-01T01:04:30Z", "1960-01-01T00:20:00-00:45[Africa/Monrovia]") // 0n — the zone's −00:44:30, which `-00:45` rounds
  * @example spanNs("2024-03-10T12:00:00Z", "invalid") // null
  */

package/dist/span/calculate/spanNs.js

@@ -32,7 +32,8 @@ import { parseInstantNanoseconds } from "../../internal/index.js";
  * - Leap seconds are not counted. UTC repeats a second rather than numbering a 61st one, so
  *   a span across one is a second short of the physical elapsed time; against a smeared
  *   clock (Google, AWS, Meta) the error is up to a second spread over the smear window.
- *   Leap-second-exact spans need a TAI scale, which GMT does not yet ship.
+ *   For a leap-second-exact span, convert both ends with `toTAI` or add
+ *   `leapSecondsBetween(start, end)` seconds, both from `timescale/`.
  *
  * @param start ISO 8601 instant string the span is measured from
  * @param end ISO 8601 instant string the span is measured to
@@ -42,8 +43,8 @@ import { parseInstantNanoseconds } from "../../internal/index.js";
  * @example spanNs("2024-03-10T12:00:01Z", "2024-03-10T12:00:00Z") // -1000000000n
  * @example spanNs("2024-03-10T12:00:00Z", "2024-03-10T12:00:00Z") // 0n
  * @example spanNs("2024-03-10T12:00:00.123456789Z", "2024-03-10T12:00:00.123456790Z") // 1n
- * @example spanNs("2024-03-10T07:00:00-05:00[America/New_York]", "2024-03-10T12:00:00Z") // 0n — same instant, different zones
- * @example spanNs("2024-03-10T12:00:00+05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]") // 32400000000000n — offsets decide, the zone is not checked
+ * @example spanNs("2024-03-10T07:00:00-05:00[America/Bogota]", "2024-03-10T12:00:00Z") // 0n — same instant, different zones
+ * @example spanNs("2024-03-10T12:00:00+05:00[Asia/Tokyo]", "2024-03-10T12:00:00-04:00[Asia/Tokyo]") // 32400000000000n — offsets decide, the zone is not checked
  * @example spanNs("1960-01-01T01:04:30Z", "1960-01-01T00:20:00-00:45[Africa/Monrovia]") // 0n — the zone's −00:44:30, which `-00:45` rounds
  * @example spanNs("2024-03-10T12:00:00Z", "invalid") // null
  */

package/dist/span/calculate/spanWallClock.d.ts

@@ -28,8 +28,8 @@ export type WallClockSpanUnit = "days" | "hours" | "day" | "hour";
  *   The wall clock is read straight off the string with `Temporal.PlainDateTime.from`. Going
  *   via `ZonedDateTime` would be a local → instant → local round trip, and that round trip is
  *   lossy at exactly the DST edges this function exists to get right: an offset-less
- *   `"2024-03-10T02:30:00[America/New_York]"` names a wall time that never occurred, and
- *   Temporal's default `compatible` disambiguation would silently advance it to `03:30`,
+ *   `"2024-03-31T01:30:00[Europe/London]"` names a wall time that never occurred, and
+ *   Temporal's default `compatible` disambiguation would silently advance it to `02:30`,
  *   turning a 24-hour answer into 23. A nonexistent or ambiguous local time is measured as
  *   written instead — for a clock-face question, the digits in the string *are* the answer.
  * - Requires a bracketed IANA time zone on both endpoints, as `isValidZonedDateTime` does —
@@ -38,8 +38,8 @@ export type WallClockSpanUnit = "days" | "hours" | "day" | "hour";
  *   `[u-ca=...]` calendar annotations are rejected; `days` and `hours` mean the same thing in
  *   every calendar system, so the annotation would change nothing.
  * - The endpoints need not share a zone. When they differ, this is the distance between two
- *   local wall clocks — a flight leaving New York at 23:00 and landing in Berlin at 11:00 the
- *   next local day is 12 wall-clock hours, and 7 elapsed hours by `spanMs`.
+ *   local wall clocks — a flight leaving São Paulo at 23:00 and landing in Berlin at 15:00 the
+ *   next local day is 16 wall-clock hours, and 12 elapsed hours by `spanMs`.
  * - Returns `null` on invalid input, not `0` — `0` is the span between a wall time and itself.
  *
  * @param start zoned ISO 8601 datetime string the span is measured from
@@ -47,14 +47,14 @@ export type WallClockSpanUnit = "days" | "hours" | "day" | "hour";
  * @param unit "days" or "hours" (or the singular "day" or "hour") of wall-clock distance
  * @returns whole wall-clock units, negative when start is after end, or null on invalid input
  *
- * @example spanWallClock("2024-03-09T12:00:00-05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]", "hours") // 24 — spanMs reports 82800000 (23 hours)
- * @example spanWallClock("2024-11-02T12:00:00-04:00[America/New_York]", "2024-11-03T12:00:00-05:00[America/New_York]", "days") // 1 — spanMs reports 90000000 (25 hours)
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T18:00:00-05:00[America/New_York]", "days") // 1 — truncated toward zero
- * @example spanWallClock("2024-03-02T18:00:00-05:00[America/New_York]", "2024-03-01T12:00:00-05:00[America/New_York]", "hours") // -30
- * @example spanWallClock("2024-03-10T23:00:00-04:00[America/New_York]", "2024-03-11T11:00:00+01:00[Europe/Berlin]", "hours") // 12 — each endpoint's own wall clock
- * @example spanWallClock("2024-03-10T02:30:00[America/New_York]", "2024-03-11T02:30:00[America/New_York]", "hours") // 24 — a wall time that never occurred is measured as written
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T12:00:00-05:00[America/New_York]", "day") // 1 — singular unit name
+ * @example spanWallClock("2024-03-30T12:00:00+00:00[Europe/London]", "2024-03-31T12:00:00+01:00[Europe/London]", "hours") // 24 — spanMs reports 82800000 (23 hours)
+ * @example spanWallClock("2024-04-06T12:00:00+11:00[Australia/Sydney]", "2024-04-07T12:00:00+10:00[Australia/Sydney]", "days") // 1 — spanMs reports 90000000 (25 hours)
+ * @example spanWallClock("2024-03-01T12:00:00+05:30[Asia/Kolkata]", "2024-03-02T18:00:00+05:30[Asia/Kolkata]", "days") // 1 — truncated toward zero
+ * @example spanWallClock("2024-03-02T18:00:00+05:30[Asia/Kolkata]", "2024-03-01T12:00:00+05:30[Asia/Kolkata]", "hours") // -30
+ * @example spanWallClock("2024-03-10T23:00:00-03:00[America/Sao_Paulo]", "2024-03-11T15:00:00+01:00[Europe/Berlin]", "hours") // 16 — each endpoint's own wall clock
+ * @example spanWallClock("2024-03-31T01:30:00[Europe/London]", "2024-04-01T01:30:00[Europe/London]", "hours") // 24 — a wall time that never occurred is measured as written
+ * @example spanWallClock("2024-03-01T12:00:00+02:00[Africa/Johannesburg]", "2024-03-02T12:00:00+02:00[Africa/Johannesburg]", "day") // 1 — singular unit name
  * @example spanWallClock("2024-03-10T12:00:00Z", "2024-03-11T12:00:00Z", "days") // null — no bracketed time zone
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T12:00:00-05:00[America/New_York]", "minutes") // null
+ * @example spanWallClock("2024-03-01T12:00:00+02:00[Africa/Johannesburg]", "2024-03-02T12:00:00+02:00[Africa/Johannesburg]", "minutes") // null
  */
 export declare function spanWallClock(start: string, end: string, unit: WallClockSpanUnit): number | null;

package/dist/span/calculate/spanWallClock.js

@@ -1,4 +1,4 @@
-import { Temporal } from "@js-temporal/polyfill";
+import { Temporal } from "../../internal/temporal.js";
 import { isValidZonedDateTime } from "../../zoned/validate/index.js";
 const WALL_CLOCK_SPAN_UNITS = {
     days: "day",
@@ -26,8 +26,8 @@ const WALL_CLOCK_SPAN_UNITS = {
  *   The wall clock is read straight off the string with `Temporal.PlainDateTime.from`. Going
  *   via `ZonedDateTime` would be a local → instant → local round trip, and that round trip is
  *   lossy at exactly the DST edges this function exists to get right: an offset-less
- *   `"2024-03-10T02:30:00[America/New_York]"` names a wall time that never occurred, and
- *   Temporal's default `compatible` disambiguation would silently advance it to `03:30`,
+ *   `"2024-03-31T01:30:00[Europe/London]"` names a wall time that never occurred, and
+ *   Temporal's default `compatible` disambiguation would silently advance it to `02:30`,
  *   turning a 24-hour answer into 23. A nonexistent or ambiguous local time is measured as
  *   written instead — for a clock-face question, the digits in the string *are* the answer.
  * - Requires a bracketed IANA time zone on both endpoints, as `isValidZonedDateTime` does —
@@ -36,8 +36,8 @@ const WALL_CLOCK_SPAN_UNITS = {
  *   `[u-ca=...]` calendar annotations are rejected; `days` and `hours` mean the same thing in
  *   every calendar system, so the annotation would change nothing.
  * - The endpoints need not share a zone. When they differ, this is the distance between two
- *   local wall clocks — a flight leaving New York at 23:00 and landing in Berlin at 11:00 the
- *   next local day is 12 wall-clock hours, and 7 elapsed hours by `spanMs`.
+ *   local wall clocks — a flight leaving São Paulo at 23:00 and landing in Berlin at 15:00 the
+ *   next local day is 16 wall-clock hours, and 12 elapsed hours by `spanMs`.
  * - Returns `null` on invalid input, not `0` — `0` is the span between a wall time and itself.
  *
  * @param start zoned ISO 8601 datetime string the span is measured from
@@ -45,15 +45,15 @@ const WALL_CLOCK_SPAN_UNITS = {
  * @param unit "days" or "hours" (or the singular "day" or "hour") of wall-clock distance
  * @returns whole wall-clock units, negative when start is after end, or null on invalid input
  *
- * @example spanWallClock("2024-03-09T12:00:00-05:00[America/New_York]", "2024-03-10T12:00:00-04:00[America/New_York]", "hours") // 24 — spanMs reports 82800000 (23 hours)
- * @example spanWallClock("2024-11-02T12:00:00-04:00[America/New_York]", "2024-11-03T12:00:00-05:00[America/New_York]", "days") // 1 — spanMs reports 90000000 (25 hours)
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T18:00:00-05:00[America/New_York]", "days") // 1 — truncated toward zero
- * @example spanWallClock("2024-03-02T18:00:00-05:00[America/New_York]", "2024-03-01T12:00:00-05:00[America/New_York]", "hours") // -30
- * @example spanWallClock("2024-03-10T23:00:00-04:00[America/New_York]", "2024-03-11T11:00:00+01:00[Europe/Berlin]", "hours") // 12 — each endpoint's own wall clock
- * @example spanWallClock("2024-03-10T02:30:00[America/New_York]", "2024-03-11T02:30:00[America/New_York]", "hours") // 24 — a wall time that never occurred is measured as written
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T12:00:00-05:00[America/New_York]", "day") // 1 — singular unit name
+ * @example spanWallClock("2024-03-30T12:00:00+00:00[Europe/London]", "2024-03-31T12:00:00+01:00[Europe/London]", "hours") // 24 — spanMs reports 82800000 (23 hours)
+ * @example spanWallClock("2024-04-06T12:00:00+11:00[Australia/Sydney]", "2024-04-07T12:00:00+10:00[Australia/Sydney]", "days") // 1 — spanMs reports 90000000 (25 hours)
+ * @example spanWallClock("2024-03-01T12:00:00+05:30[Asia/Kolkata]", "2024-03-02T18:00:00+05:30[Asia/Kolkata]", "days") // 1 — truncated toward zero
+ * @example spanWallClock("2024-03-02T18:00:00+05:30[Asia/Kolkata]", "2024-03-01T12:00:00+05:30[Asia/Kolkata]", "hours") // -30
+ * @example spanWallClock("2024-03-10T23:00:00-03:00[America/Sao_Paulo]", "2024-03-11T15:00:00+01:00[Europe/Berlin]", "hours") // 16 — each endpoint's own wall clock
+ * @example spanWallClock("2024-03-31T01:30:00[Europe/London]", "2024-04-01T01:30:00[Europe/London]", "hours") // 24 — a wall time that never occurred is measured as written
+ * @example spanWallClock("2024-03-01T12:00:00+02:00[Africa/Johannesburg]", "2024-03-02T12:00:00+02:00[Africa/Johannesburg]", "day") // 1 — singular unit name
  * @example spanWallClock("2024-03-10T12:00:00Z", "2024-03-11T12:00:00Z", "days") // null — no bracketed time zone
- * @example spanWallClock("2024-03-01T12:00:00-05:00[America/New_York]", "2024-03-02T12:00:00-05:00[America/New_York]", "minutes") // null
+ * @example spanWallClock("2024-03-01T12:00:00+02:00[Africa/Johannesburg]", "2024-03-02T12:00:00+02:00[Africa/Johannesburg]", "minutes") // null
  */
 export function spanWallClock(start, end, unit) {
     if (typeof unit !== "string") {

package/dist/span/index.d.ts

@@ -1,3 +1,3 @@
-export * from "@js-temporal/polyfill";
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calculate/index.js";
 export * from "./validate/index.js";

package/dist/span/index.js

@@ -1,4 +1,4 @@
-// Re-export the Temporal polyfill (`Temporal`, `Intl`, `toTemporalInstant`) so every namespace subpath offers it
-export * from "@js-temporal/polyfill";
+// Re-export `Temporal`, `Intl` and `toTemporalInstant` from the internal seam so every namespace subpath offers them
+export { Intl, Temporal, toTemporalInstant } from "../internal/temporal.js";
 export * from "./calculate/index.js";
 export * from "./validate/index.js";