daymath 0.7.1 → 0.7.2

package/README.md

@@ -360,6 +360,52 @@ would not escape this. Bundlers and browsers are unaffected. A Jest consumer nee
 
 Node 18 was supported through 0.3.0 and is dropped here. It went end-of-life in April 2025.
 
+### In a browser, from a CDN
+
+The `?bundle` is not optional.
+
+```html
+<script type="module">
+  import * as daymath from 'https://esm.sh/daymath?bundle'
+  console.log(daymath.addDays('2026-08-06', 7))
+</script>
+```
+
+The answer that snippet logs, asserted by `npm run test:examples`, because a claim inside an html
+fence is not:
+
+```js
+addDays('2026-08-06', 7) // '2026-08-13'
+```
+
+Most CDNs serve a daymath that throws on every date, and the message it throws is not helpful.
+daymath imports two subpaths of `temporal-polyfill`, `fns/PlainDate` and `fns/Calendar`. A CDN that
+rebuilds each subpath into its own bundle gives each one a private copy of the polyfill's internals,
+so the calendar built by one copy is unrecognisable to the other and `fromString` throws
+`TypeError: Invalid calling context`. No import spelling avoids it: `temporal-polyfill/fns` is in
+the export map but its file is empty, so the separate subpaths are the whole `fns` API.
+
+Measured 2026-09-05. `npm run test:demo` re-checks the first row on a schedule; the other four rows
+carry no gate, so re-measure them rather than trusting the table:
+
+```
+for u in "https://esm.sh/daymath?bundle" "https://unpkg.com/daymath?module" "https://esm.sh/daymath" "https://esm.run/daymath" "https://cdn.jsdelivr.net/npm/daymath/+esm"; do
+  node scripts/demo-page.mjs --url "$u" >/dev/null 2>&1 && echo "yes $u" || echo "no  $u"
+done
+```
+
+
+| URL | Works |
+| --- | --- |
+| `https://esm.sh/daymath?bundle` | yes |
+| `https://unpkg.com/daymath?module` | yes |
+| `https://esm.sh/daymath` | no |
+| `https://esm.run/daymath` | no |
+| `https://cdn.jsdelivr.net/npm/daymath/+esm` | no |
+
+A bundler is unaffected. It resolves both subpaths through one copy in `node_modules`, which is why
+every gate in this repo stayed green while the demo page was dead.
+
 ## Types & tests
 
 Plain JS + `index.d.ts` (no compile step). CI runs on Node 20, 22, 24, and 26; the

package/index.js

@@ -401,6 +401,13 @@ function toPlainDate(value, label = 'date') {
       ? plain
       : PlainDateFns.withCalendar(plain, getAny(calendar))
   } catch (err) {
+    // Temporal reports every input fault here as a RangeError, so anything else is the
+    // implementation breaking and must surface unchanged. A CDN serving two copies of
+    // `temporal-polyfill/fns` throws `TypeError: Invalid calling context`; the old catch-all
+    // relabelled that as `invalid date` and sent the reader after their own input instead.
+    // Ignored for coverage because a healthy Temporal cannot reach it.
+    /* c8 ignore next */
+    if (!(err instanceof RangeError)) throw err
     throw new RangeError(`daymath: invalid ${label} ${JSON.stringify(text)}`, {
       cause: err,
     })

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "daymath",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "Calendar date math (ISO 8601 day / PlainDate). date-fns-shaped. No Date. No time zones.",
   "type": "module",
   "main": "./index.js",
@@ -30,6 +30,7 @@
     "test:runtimes:write": "node scripts/cross-runtime.mjs --write",
     "test:intl-day": "node scripts/intl-day.mjs",
     "test:examples": "node scripts/examples.mjs",
+    "test:demo": "node scripts/demo-page.mjs",
     "test:examples:write": "node scripts/examples.mjs --write",
     "test:intl-day:sweep": "node scripts/intl-day.mjs --sweep",
     "size": "node scripts/bundle-size.mjs --run",
@@ -70,8 +71,8 @@
     "c8": "^12.0.0",
     "date-fns": "4.4.0",
     "esbuild": "0.28.2",
-    "oxfmt": "0.64.0",
-    "oxlint": "1.78.0",
+    "oxfmt": "0.65.0",
+    "oxlint": "1.81.0",
     "typescript": "7.0.2"
   }
 }