@ultimat3/time 20.2.1 → 22.0.0

package/README.md

@@ -158,6 +158,15 @@ negated; an empty one is `0` in either direction, never `-0`.
 | `X_CRON_NOT_DESCRIBABLE` | a valid 6-field cron whose seconds field `CronPhrases` has no words for |
 | `X_SCHEDULE_INVALID` | a wall-clock field out of range: `slot.hour`, `slot.minute`, `slot.second`, `slot.weekday` |
 
+### Error classes
+
+Every error class `src/index.ts` exports, for `instanceof` inside one process. Across a wire or
+a job boundary the class is gone and the `code` is what survives — match on that.
+
+| Class | Code | Declared in |
+|---|---|---|
+| `TimeError` | any `TimeErrorCode` — `TIME_ERROR_CODES` | `src/errors.ts` |
+
 ## Why it exists
 
 Naive time math breaks quietly: the digest goes out an hour early for half the year, the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/time",
-  "version": "20.2.1",
+  "version": "22.0.0",
   "description": "UTC instants, DST-correct zone math, cron, durations and Intl formatting with an explicit timezone",
   "license": "MIT",
   "type": "module",
@@ -34,6 +34,7 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "20.2.1"
+    "@ultimat3/core": "22.0.0",
+    "@ultimat3/schema": "22.0.0"
   }
 }

package/src/instant.ts

@@ -5,6 +5,7 @@
  */
 
 import { type Clock, systemClock } from '@ultimat3/core';
+import { isIsoDateTime } from '@ultimat3/schema';
 import { instantInvalid } from './errors';
 
 declare const instantBrand: unique symbol;
@@ -25,19 +26,13 @@ export function instant(value: Date): Instant {
 }
 
 /**
- * A time of day, and the zone it is stated in. `2026-03-14T09:00` without one is resolved by
- * `new Date` through the PROCESS's zone, so the guard has to see both halves: a string carrying
- * a clock time is refused unless it also carries `Z` or an offset. A date-only form carries no
- * clock time and is UTC by specification, so it passes.
+ * ISO-8601 in, `Instant` out. An offset or `Z` is required — a bare local string is refused — and
+ * so is anything that is not the ISO shape at all: `new Date` also parses `'March 14, 2026'`,
+ * `'3/14/2026'` and `'12'`, each at the HOST's local midnight. The rule is `@ultimat3/schema`'s
+ * `isIsoDateTime`, the one `t.date` and HTTP coercion answer with, so the three cannot disagree.
  */
-const CLOCK_TIME = /[t ]\d{1,2}:\d{2}/i;
-const UTC_OFFSET = /(?:z|[+-]\d{2}:?\d{2})$/i;
-
-/** ISO-8601 in, `Instant` out. An offset or `Z` is required — a bare local string is refused. */
 export function fromIso(iso: string): Instant {
-  // Enforced, not documented: this header asked for an offset for three releases while the body
-  // accepted a bare local string and answered a different instant per deployment timezone.
-  if (CLOCK_TIME.test(iso) && !UTC_OFFSET.test(iso)) throw instantInvalid(iso);
+  if (!isIsoDateTime(iso)) throw instantInvalid(iso);
   const parsed = new Date(iso);
   if (Number.isNaN(parsed.getTime())) throw instantInvalid(iso);
   return parsed as Instant;