@northguild/gmt 1.18.0 → 1.19.0

package/dist/unix/calculate/diffUnix.d.ts

@@ -35,6 +35,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * - Each value is a safe integer or a digit string (`"1706659200000"`); anything else is invalid.
  * - Unit names may be singular or plural (`"day"` or `"days"`), as in Temporal; a record result
  *   keeps the plural keys.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value1 first Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param value2 second Unix epoch, in the same form and unit
@@ -58,8 +64,10 @@ export declare function diffUnix(value1: number | string, value2: number | strin
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone calendar units are measured in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone calendar units are measured in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/diffUnix.js

@@ -1,6 +1,5 @@
-import { addToZoned, resolveDurationUnit, zonedUntil } from "../../internal/index.js";
+import { addToZoned, frameZoned, normalizeZoneFrame, resolveDurationUnit, zonedUntil, } from "../../internal/index.js";
 import { differenceRecord } from "../../internal/differenceRecord.js";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
 import { resolveUnixEpochUnit, unixEpochToInstant, } from "../../internal/unixEpochValue.js";
 import { getLargestDateTimeDurationUnit } from "../../plain/calculate/getLargestDateTimeDurationUnit.js";
 import { isValidDateTimeDurationUnit } from "../../plain/validate/index.js";
@@ -39,6 +38,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * - Each value is a safe integer or a digit string (`"1706659200000"`); anything else is invalid.
  * - Unit names may be singular or plural (`"day"` or `"days"`), as in Temporal; a record result
  *   keeps the plural keys.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value1 first Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param value2 second Unix epoch, in the same form and unit
@@ -60,8 +65,8 @@ export function diffUnix(value1, value2, units, options) {
             return null;
         }
         const epochUnit = resolveUnixEpochUnit(options?.epochUnit);
-        const timeZone = normalizeTimeZone(options?.timeZone);
-        if (!timeZone || epochUnit === null)
+        const frame = normalizeZoneFrame(options?.timeZone);
+        if (frame === null || epochUnit === null)
             return null;
         const requested = Array.isArray(units) ? units : [units];
         const plurals = requested.map((unit) => typeof unit === "string" ? resolveDurationUnit(unit) : "");
@@ -77,7 +82,7 @@ export function diffUnix(value1, value2, units, options) {
         if (largestUnit === "")
             return null;
         try {
-            const duration = zonedUntil(instant1.toZonedDateTimeISO(timeZone), instant2.toZonedDateTimeISO(timeZone), {
+            const duration = zonedUntil(frameZoned(instant1, frame), frameZoned(instant2, frame), {
                 largestUnit,
                 smallestUnit: options?.smallestUnit,
                 roundingIncrement: options?.roundingIncrement,
@@ -87,7 +92,7 @@ export function diffUnix(value1, value2, units, options) {
                 return duration[plurals[0]] ?? 0;
             }
             // An unlisted unit between two listed units is carried into the next smaller listed unit.
-            const start = instant1.toZonedDateTimeISO(timeZone);
+            const start = frameZoned(instant1, frame);
             // Record keys are the plural names, as in every other diff family.
             return differenceRecord(start, duration, plurals, {
                 add: (from, amount) => addToZoned(from, amount),

package/dist/unix/calculate/diffUnixAsDuration.d.ts

@@ -24,6 +24,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * different Temporal types.
  * - Each value is a safe integer or a digit string (`"1706659200000"`); anything else is invalid.
  * - Unit names may be singular or plural (`"day"` or `"days"`), as in Temporal.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `""`. An offset to the minute has no
+ *   such limit.
  *
  * @param value1 first Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param value2 second Unix epoch, in the same form and unit
@@ -46,8 +52,10 @@ export declare function diffUnixAsDuration(value1: number | string, value2: numb
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone calendar units are measured in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone calendar units are measured in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/diffUnixAsDuration.js

@@ -1,5 +1,4 @@
-import { durationUntilString, resolveDurationUnit } from "../../internal/index.js";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { durationUntilString, frameZoned, normalizeZoneFrame, resolveDurationUnit, } from "../../internal/index.js";
 import { resolveUnixEpochUnit, unixEpochToInstant, } from "../../internal/unixEpochValue.js";
 import { isValidDateTimeDurationUnit } from "../../plain/validate/index.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
@@ -26,6 +25,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * different Temporal types.
  * - Each value is a safe integer or a digit string (`"1706659200000"`); anything else is invalid.
  * - Unit names may be singular or plural (`"day"` or `"days"`), as in Temporal.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `""`. An offset to the minute has no
+ *   such limit.
  *
  * @param value1 first Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param value2 second Unix epoch, in the same form and unit
@@ -46,8 +51,8 @@ export function diffUnixAsDuration(value1, value2, unit, options) {
             return "";
         }
         const epochUnit = resolveUnixEpochUnit(options?.epochUnit);
-        const timeZone = normalizeTimeZone(options?.timeZone);
-        if (!timeZone || epochUnit === null)
+        const frame = normalizeZoneFrame(options?.timeZone);
+        if (frame === null || epochUnit === null)
             return "";
         const largestUnit = typeof unit === "string" ? resolveDurationUnit(unit) : unit;
         if (!isValidDateTimeDurationUnit(largestUnit)) {
@@ -59,7 +64,7 @@ export function diffUnixAsDuration(value1, value2, unit, options) {
             return "";
         }
         try {
-            return durationUntilString(instant1.toZonedDateTimeISO(timeZone), instant2.toZonedDateTimeISO(timeZone), largestUnit, options);
+            return durationUntilString(frameZoned(instant1, frame), frameZoned(instant2, frame), largestUnit, options);
         }
         catch {
             return "";

package/dist/unix/calculate/endOfQuarterForUnix.d.ts

@@ -9,6 +9,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options optional: how `value` is read and the zone the quarter is found in
@@ -28,8 +34,10 @@ export declare function endOfQuarterForUnix(value: number | string, options?: {
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the unit boundaries are found in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the unit boundaries are found in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/endOfQuarterForUnix.js

@@ -10,6 +10,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options optional: how `value` is read and the zone the quarter is found in

package/dist/unix/calculate/endOfUnix.d.ts

@@ -10,6 +10,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param unit Temporal.DateUnit | Temporal.TimeUnit to specify the end
@@ -24,6 +30,7 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * @example endOfUnix(1706780800, "days", { epochUnit: "second" }) // 1706831999 (plural unit, singular epochUnit, UTC by default)
  * @example endOfUnix(1706659200000, "quarter") // null (use endOfQuarterForUnix)
  * @example endOfUnix(NaN, "day") // null
+ * @example endOfUnix(45870000, "day", { timeZone: "-00:44:30" }) // 89069999 (a stored offset with seconds)
  */
 export declare function endOfUnix(value: number | string, unit: Temporal.DateTimeUnit | Temporal.PluralUnit<Temporal.DateTimeUnit>, options?: {
     /**
@@ -34,8 +41,10 @@ export declare function endOfUnix(value: number | string, unit: Temporal.DateTim
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the unit boundaries are found in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the unit boundaries are found in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/endOfUnix.js

@@ -12,6 +12,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param unit Temporal.DateUnit | Temporal.TimeUnit to specify the end
@@ -26,6 +32,7 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * @example endOfUnix(1706780800, "days", { epochUnit: "second" }) // 1706831999 (plural unit, singular epochUnit, UTC by default)
  * @example endOfUnix(1706659200000, "quarter") // null (use endOfQuarterForUnix)
  * @example endOfUnix(NaN, "day") // null
+ * @example endOfUnix(45870000, "day", { timeZone: "-00:44:30" }) // 89069999 (a stored offset with seconds)
  */
 export function endOfUnix(value, unit, options) {
     try {

package/dist/unix/calculate/isBetweenUnix.d.ts

@@ -28,8 +28,9 @@ export declare function isBetweenUnix(value: number | string, start: number | st
     epochUnit?: UnixUnit;
     /**
      * A time zone that is validated only: the comparison is on exact instants, so the zone never
-     * changes the result. It is an IANA name, a UTC offset, or `"local"` for the system time zone.
-     * An unknown zone returns `false`.
+     * changes the result. It is an IANA name, a UTC offset (a time zone identifier such as
+     * `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what `getTimeZoneOffset`
+     * returns), or `"local"` for the system time zone. An unknown zone returns `false`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/isBetweenUnix.js

@@ -1,6 +1,6 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
 import { Temporal } from "@js-temporal/polyfill";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { normalizeZoneFrame } from "../../internal/zoneFrame.js";
 import { resolveUnixEpochUnit, unixEpochToInstant, } from "../../internal/unixEpochValue.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 import { optionOrDefault } from "../../internal/optionOrDefault.js";
@@ -29,14 +29,14 @@ export function isBetweenUnix(value, start, end, options) {
             return false;
         }
         const epochUnit = resolveUnixEpochUnit(options?.epochUnit);
-        const timeZone = normalizeTimeZone(options?.timeZone);
+        const frame = normalizeZoneFrame(options?.timeZone);
         // Only an omitted flag takes the `true` default. An explicit `null` is a value, and every
         // reading of it gives `false`: ECMA-402 reads a boolean option through ToBoolean (null → false),
         // and the house rule rejects an invalid member outright — neither yields `true`. So `null`
         // behaves here exactly as `0` and `""` already do.
         const inclusiveStart = optionOrDefault(options?.inclusiveStart, true);
         const inclusiveEnd = optionOrDefault(options?.inclusiveEnd, true);
-        if (!timeZone || epochUnit === null)
+        if (frame === null || epochUnit === null)
             return false;
         const instant = unixEpochToInstant(value, epochUnit);
         const startInstant = unixEpochToInstant(start, epochUnit);

package/dist/unix/calculate/roundUnix.d.ts

@@ -15,6 +15,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   Use `floorToZone` for a boundary that never exceeds the instant.
  * - `value` is a safe integer or a digit string (`"1706661000000"`); anything else returns null.
  * - Returns null for invalid input.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options rounding settings: the unit to round to, how to round, and how `value` is read
@@ -60,8 +66,10 @@ export declare function roundUnix(value: number | string, options: {
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the wall clock is rounded in: an IANA name, a UTC offset, or `"local"` for the
-     * system time zone. An unknown zone returns `null`.
+     * The time zone the wall clock is rounded in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/roundUnix.js

@@ -1,6 +1,5 @@
 import { isValidDateTimeUnit } from "../../plain/index.js";
-import { isObject, resolveDateTimeUnit, roundZonedDateTime, } from "../../internal/index.js";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { frameInstant, frameZoned, isObject, normalizeZoneFrame, resolveDateTimeUnit, roundZonedDateTime, } from "../../internal/index.js";
 import { resolveUnixEpochUnit, toUnixEpoch, unixEpochToInstant, } from "../../internal/unixEpochValue.js";
 const ZONED_ROUNDING_UNITS = [
     "day",
@@ -29,6 +28,12 @@ function isZonedRoundingUnit(unit) {
  *   Use `floorToZone` for a boundary that never exceeds the instant.
  * - `value` is a safe integer or a digit string (`"1706661000000"`); anything else returns null.
  * - Returns null for invalid input.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options rounding settings: the unit to round to, how to round, and how `value` is read
@@ -50,10 +55,12 @@ export function roundUnix(value, options) {
             return null;
         const { roundingIncrement, roundingMode } = options;
         const epochUnit = resolveUnixEpochUnit(options.epochUnit);
-        const timeZone = normalizeTimeZone(options.timeZone);
+        const frame = normalizeZoneFrame(options.timeZone);
         // One read (GetOption): resolveDateTimeUnit returns a value that is not a string unchanged.
         const smallestUnit = resolveDateTimeUnit(options.smallestUnit);
-        if (!timeZone || epochUnit === null || !isValidDateTimeUnit(smallestUnit)) {
+        if (frame === null ||
+            epochUnit === null ||
+            !isValidDateTimeUnit(smallestUnit)) {
             return null;
         }
         // Temporal ZonedDateTime.prototype.round: ValidateTemporalUnitValue(smallestUnit, ~time~, « day »)
@@ -65,12 +72,12 @@ export function roundUnix(value, options) {
             return null;
         }
         try {
-            const result = roundZonedDateTime(instant.toZonedDateTimeISO(timeZone), {
+            const result = roundZonedDateTime(frameZoned(instant, frame), {
                 smallestUnit,
                 roundingIncrement,
                 roundingMode,
             });
-            return toUnixEpoch(result, epochUnit);
+            return toUnixEpoch(frameInstant(result, frame), epochUnit);
         }
         catch {
             return null;

package/dist/unix/calculate/setUnix.d.ts

@@ -10,10 +10,28 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   why order-independent field resolution matters, and why `disambiguation`/`offset` require
  *   `.with()` rather than arithmetic.
  * - `fields` may set any of `year`, `month`, `monthCode`, `day`, `hour`, `minute`, `second`,
- *   `millisecond`, `microsecond`, `nanosecond`, `era`, and/or `eraYear`; omitted fields keep
- *   their current value. An empty object is a no-op.
+ *   `millisecond`, `microsecond` and/or `nanosecond`; omitted fields keep their current value. An
+ *   object with no field set, such as `{}` or `{ year: undefined }`, is a no-op.
+ * - Values are not converted: `monthCode` must be a string and every other field an integer number.
+ *   `null`, a numeric string, a boolean or a fraction returns null, where Temporal would convert or
+ *   truncate it. A bigint, `NaN` or an infinity returns null too. A number too large for its
+ *   field follows `overflow`. A month or day below 1, or a date outside Temporal's range, returns
+ *   null.
+ * - An own key that is not one of these fields, such as a misspelt `yaer`, returns null. So does an
+ *   era, an `offset`, or a `calendar` or `timeZone` property, whether own, inherited or a getter. A
+ *   field is read with a property get, as Temporal reads it, so an inherited or getter field is
+ *   set.
+ * - A Temporal date or time object returns null, as Temporal's `with` refuses one. One whose
+ *   prototype has been replaced with `Object.prototype`, `null` or `Function.prototype` sets
+ *   nothing instead.
  * - `value` is a safe integer or a digit string (`"1710072000000"`); anything else returns null.
  * - Returns null for invalid input.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param fields Partial<Temporal.ZonedDateTimeLike> object (excluding calendar/timeZone/offset) specifying fields to set
@@ -25,9 +43,10 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * @example setUnix(1706659200000, {}, { timeZone: "UTC" }) // 1706659200000 (empty fields object is a no-op)
  * @example setUnix(1730615400000, { minute: 45 }, { timeZone: "America/New_York" }) // 1730616300000 (the second 01:30 keeps -05:00)
  * @example setUnix(1730615400000, { minute: 45 }, { timeZone: "America/New_York", offset: "ignore" }) // 1730612700000 (re-resolved: the earlier 01:45)
+ * @example setUnix(1710072000000, { hour: "9" }, { timeZone: "UTC" }) // null (not converted)
  * @example setUnix(NaN, { hour: 9 }) // null
  */
-export declare function setUnix(value: number | string, fields: Omit<Temporal.ZonedDateTimeLike, "calendar" | "timeZone" | "offset">, options?: {
+export declare function setUnix(value: number | string, fields: Omit<Temporal.ZonedDateTimeLike, "calendar" | "timeZone" | "offset" | "era" | "eraYear">, options?: {
     /**
      * The unit the epoch values are counted in: `"seconds"` or `"milliseconds"`, singular or
      * plural. Any other value returns `null`. The result is in the same unit.
@@ -36,8 +55,9 @@ export declare function setUnix(value: number | string, fields: Omit<Temporal.Zo
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the fields are set in: an IANA name, a UTC offset, or `"local"` for the system
-     * time zone. An unknown zone returns `null`.
+     * The time zone the fields are set in: an IANA name, a UTC offset (a time zone identifier such
+     * as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what `getTimeZoneOffset`
+     * returns), or `"local"` for the system time zone. An unknown zone returns `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/setUnix.js

@@ -1,5 +1,4 @@
-import { resolveOverflow, withZonedFields } from "../../internal/index.js";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { DATE_TIME_FIELDS, frameInstant, frameZoned, normalizeZoneFrame, readSetFields, resolveOverflow, withZonedFields, } from "../../internal/index.js";
 import { resolveUnixEpochUnit, toUnixEpoch, unixEpochToInstant, } from "../../internal/unixEpochValue.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 import { optionOrDefault } from "../../internal/optionOrDefault.js";
@@ -12,10 +11,28 @@ import { optionOrDefault } from "../../internal/optionOrDefault.js";
  *   why order-independent field resolution matters, and why `disambiguation`/`offset` require
  *   `.with()` rather than arithmetic.
  * - `fields` may set any of `year`, `month`, `monthCode`, `day`, `hour`, `minute`, `second`,
- *   `millisecond`, `microsecond`, `nanosecond`, `era`, and/or `eraYear`; omitted fields keep
- *   their current value. An empty object is a no-op.
+ *   `millisecond`, `microsecond` and/or `nanosecond`; omitted fields keep their current value. An
+ *   object with no field set, such as `{}` or `{ year: undefined }`, is a no-op.
+ * - Values are not converted: `monthCode` must be a string and every other field an integer number.
+ *   `null`, a numeric string, a boolean or a fraction returns null, where Temporal would convert or
+ *   truncate it. A bigint, `NaN` or an infinity returns null too. A number too large for its
+ *   field follows `overflow`. A month or day below 1, or a date outside Temporal's range, returns
+ *   null.
+ * - An own key that is not one of these fields, such as a misspelt `yaer`, returns null. So does an
+ *   era, an `offset`, or a `calendar` or `timeZone` property, whether own, inherited or a getter. A
+ *   field is read with a property get, as Temporal reads it, so an inherited or getter field is
+ *   set.
+ * - A Temporal date or time object returns null, as Temporal's `with` refuses one. One whose
+ *   prototype has been replaced with `Object.prototype`, `null` or `Function.prototype` sets
+ *   nothing instead.
  * - `value` is a safe integer or a digit string (`"1710072000000"`); anything else returns null.
  * - Returns null for invalid input.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param fields Partial<Temporal.ZonedDateTimeLike> object (excluding calendar/timeZone/offset) specifying fields to set
@@ -27,6 +44,7 @@ import { optionOrDefault } from "../../internal/optionOrDefault.js";
  * @example setUnix(1706659200000, {}, { timeZone: "UTC" }) // 1706659200000 (empty fields object is a no-op)
  * @example setUnix(1730615400000, { minute: 45 }, { timeZone: "America/New_York" }) // 1730616300000 (the second 01:30 keeps -05:00)
  * @example setUnix(1730615400000, { minute: 45 }, { timeZone: "America/New_York", offset: "ignore" }) // 1730612700000 (re-resolved: the earlier 01:45)
+ * @example setUnix(1710072000000, { hour: "9" }, { timeZone: "UTC" }) // null (not converted)
  * @example setUnix(NaN, { hour: 9 }) // null
  */
 export function setUnix(value, fields, options) {
@@ -35,8 +53,8 @@ export function setUnix(value, fields, options) {
             return null;
         }
         const epochUnit = resolveUnixEpochUnit(options?.epochUnit);
-        const timeZone = normalizeTimeZone(options?.timeZone);
-        if (!timeZone || epochUnit === null)
+        const frame = normalizeZoneFrame(options?.timeZone);
+        if (frame === null || epochUnit === null)
             return null;
         const instant = unixEpochToInstant(value, epochUnit);
         if (instant === null)
@@ -46,17 +64,20 @@ export function setUnix(value, fields, options) {
         // Temporal ZonedDateTime.prototype.with: GetTemporalOffsetOption(options, "prefer").
         const offset = optionOrDefault(options?.offset, "prefer");
         try {
-            const zoned = instant.toZonedDateTimeISO(timeZone);
-            // Temporal.ZonedDateTime.prototype.with() throws on an empty fields object ("no supported
-            // properties found") rather than treating it as a no-op, so short-circuit here.
-            const result = Object.keys(fields).length === 0
+            const zoned = frameZoned(instant, frame);
+            const set = readSetFields(fields, DATE_TIME_FIELDS);
+            if (set === null)
+                return null;
+            // Only the values readSetFields checked reach Temporal, on both paths of withZonedFields. An
+            // empty result sets nothing: a no-op here, where Temporal's with() would throw.
+            const result = Object.keys(set).length === 0
                 ? zoned
-                : withZonedFields(zoned, fields, {
+                : withZonedFields(zoned, set, {
                     overflow,
                     disambiguation,
                     offset,
                 });
-            return toUnixEpoch(result, epochUnit);
+            return toUnixEpoch(frameInstant(result, frame), epochUnit);
         }
         catch {
             return null;

package/dist/unix/calculate/startOfQuarterForUnix.d.ts

@@ -9,6 +9,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options optional: how `value` is read and the zone the quarter is found in
@@ -29,8 +35,10 @@ export declare function startOfQuarterForUnix(value: number | string, options?:
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the unit boundaries are found in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the unit boundaries are found in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/startOfQuarterForUnix.js

@@ -10,6 +10,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param options optional: how `value` is read and the zone the quarter is found in

package/dist/unix/calculate/startOfUnix.d.ts

@@ -10,6 +10,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param unit Temporal.DateUnit | Temporal.TimeUnit to specify the start
@@ -24,6 +30,7 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * @example startOfUnix(1706780800, "days", { epochUnit: "second" }) // 1706745600 (plural unit, singular epochUnit, UTC by default)
  * @example startOfUnix(1706659200000, "quarter") // null (use startOfQuarterForUnix)
  * @example startOfUnix(NaN, "day") // null
+ * @example startOfUnix(45870000, "day", { timeZone: "-00:44:30" }) // 2670000 (local midnight at a stored offset with seconds)
  */
 export declare function startOfUnix(value: number | string, unit: Temporal.DateTimeUnit | Temporal.PluralUnit<Temporal.DateTimeUnit>, options?: {
     /**
@@ -34,8 +41,10 @@ export declare function startOfUnix(value: number | string, unit: Temporal.DateT
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the unit boundaries are found in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the unit boundaries are found in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/unix/calculate/startOfUnix.js

@@ -12,6 +12,12 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  *   takes neither. Those ignored options were removed in 1.16.0.
  * - Returns null for invalid input.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param unit Temporal.DateUnit | Temporal.TimeUnit to specify the start
@@ -26,6 +32,7 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * @example startOfUnix(1706780800, "days", { epochUnit: "second" }) // 1706745600 (plural unit, singular epochUnit, UTC by default)
  * @example startOfUnix(1706659200000, "quarter") // null (use startOfQuarterForUnix)
  * @example startOfUnix(NaN, "day") // null
+ * @example startOfUnix(45870000, "day", { timeZone: "-00:44:30" }) // 2670000 (local midnight at a stored offset with seconds)
  */
 export function startOfUnix(value, unit, options) {
     try {

package/dist/unix/calculate/subtractUnix.d.ts

@@ -7,6 +7,12 @@ import type { UnixUnit } from "../validate/isValidUnixUnit.js";
  * - Validates duration units and values.
  * - `value` is a safe integer or a digit string (`"1706659200000"`); anything else returns null.
  * - Returns null for invalid input.
+ * - **Limit at an offset with seconds.** The instant is placed in the offset's whole-minute zone,
+ *   moved by its seconds, and the moved instant must be inside Temporal's range. So within the
+ *   offset's seconds (under a minute) of the last instant Temporal supports
+ *   (`+275760-09-13T00:00:00Z`) for an offset east of UTC, or of the first
+ *   (`-271821-04-20T00:00:00Z`) for one west, this returns `null`. An offset to the minute has no
+ *   such limit.
  *
  * @param value Unix epoch: a safe integer, or a string of optionally negative ASCII digits
  * @param units Partial<Record<DateTimeDurationUnit, number>> object specifying units to subtract
@@ -29,8 +35,10 @@ export declare function subtractUnix(value: number | string, units: Partial<Reco
      */
     epochUnit?: UnixUnit;
     /**
-     * The time zone the calendar arithmetic runs in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the calendar arithmetic runs in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */