@ultimat3/time
Advanced tools
+5
-1
@@ -39,3 +39,7 @@ # @ultimat3/time — agent notes | ||
| the direction that fails dangerous: an abbreviation names no DST rule. So the judgement is never | ||
| delegated to `Intl`. `canonicalTimeZone` asserts the structural property itself: a zone is | ||
| delegated to `Intl`. Re-measured 2026-08-27 when the Bun 1.3 reversal was trialled: | ||
| `new Intl.DateTimeFormat('en', { timeZone: 'CET' })` still THROWS on 1.3.14 and resolves on 1.4.0, | ||
| while both list the same 445 zones — so the two ICUs disagree in the direction this rule already | ||
| refuses, and a structural judgement is the only thing that answers the same on either runtime. | ||
| That is the whole argument, and it is why the trial changed nothing here. `canonicalTimeZone` asserts the structural property itself: a zone is | ||
| `Area/Location`, and `UTC` is the one legal exception. Never a denylist of the names ICU newly | ||
@@ -42,0 +46,0 @@ accepts — that list grows with every tzdata and ICU release, and no rule in it keeps `CET` out |
+2
-2
| { | ||
| "name": "@ultimat3/time", | ||
| "version": "18.0.0", | ||
| "version": "19.0.0", | ||
| "description": "UTC instants, DST-correct zone math, cron, durations and Intl formatting with an explicit timezone", | ||
@@ -37,4 +37,4 @@ "license": "MIT", | ||
| "dependencies": { | ||
| "@ultimat3/core": "18.0.0" | ||
| "@ultimat3/core": "19.0.0" | ||
| } | ||
| } |
120642
0.36%+ Added
+ Added
- Removed
- Removed
Updated