tosijs-ui 1.15.0 → 1.15.2

package/CHANGELOG.md

@@ -1,5 +1,76 @@
 # Changelog
 
+## 1.15.2
+
+### The `tjs-lang` peer admits 0.14.x (#182)
+
+**Upgrade before, or together with, tjs-lang 0.14.0** — if you install with npm and have
+`tjs-lang` installed.
+
+The optional peer was `^0.13.1`, and a caret on a `0.x` version admits patches only, so it
+could not reach 0.14.0. An optional peer is only optional when it is *absent*: when it is
+present and out of range, npm 7+ fails the install with `ERESOLVE`. It is now
+`^0.13.1 || ^0.14.0`. bun resolves either way, which is why nothing here surfaced it; tjs-lang's
+own pre-release review found it (the same defect as #98, one minor later).
+
+Verified against `tjs-lang@0.14.0-rc.0` before widening: typecheck, build, unit, Playwright on
+all three engines (the whole doc-test tier included) and the haltija lane all pass against it.
+The one break 0.14.0 names, runtime types becoming callable, touches nothing here: no tosijs-ui
+code handles a tjs runtime type.
+
+The live-example CDN pin and the dev dependency stay on 0.13.13 until 0.14.0 is final, so a
+published doc site keeps fetching the version it was built and tested against.
+
+### The installed `bin/docs.ts` shim resolves its import
+
+The back-compat shim for `extractDocs` importers re-exported from `../src/…`, and `src/` is not
+in the published package, so since the doc-site system moved into `tosijs-ui/site` (June) it
+threw `Cannot find module` for every installed consumer. It now re-exports from `dist/`, so
+running it with `bun` or importing it by file path works. The bare specifier
+`'tosijs-ui/bin/docs'` still does not resolve (the `exports` map sends it to `dist/`), and never
+has since that map was added. **Use `tosijs-ui/site`** — it was never affected.
+
+Found by a release check that had been silently skipping; it runs now.
+
+### `tosijs-tunnel`, `tosijs-deploy`, `tosijs-caddy-install`, `tosijs-release-notes`: import spelling only
+
+These bins now import `./resolve-site-config.ts` with its extension instead of relying on Bun's
+extension probing, so each relative specifier names a file that is in the package. **No
+behaviour moved:** the same module is loaded, and nothing in argument handling, ports, hosts,
+secrets or what they write was touched. The diff is the import line in each file. Found by the
+same check.
+
+## 1.15.1
+
+### Doc-test failures reported the wrong line — the same wrong line, every time (#142)
+
+Reported by an adopter converting a WebGL project to test fences: two failures in two
+*different* blocks both named `(line 114)`. Reproduced in Chromium — blocks failing at lines 2
+and 10 both reported **131**.
+
+Nothing was being recognised as the user's frame, so the first bundle frame won and every
+failure named one constant wrong line. The cause is narrow and unlucky: the only mechanism was
+a list of bundle filenames to skip, it matched a bare `/iife.js`, and a doc site serves
+`/iife.js?v=<hash>` — the cache-busting stamp — which the `$` anchor rejects. It also never
+listed `hydrate.js`, which is the bundle an *adopter's* site actually loads. So on a real doc
+site nothing was skipped at all.
+
+The user's frame is now identified **positively**, by the `sourceURL` the code was tagged with,
+which is immune to query strings, to bundle names we did not anticipate, and to whatever an
+adopter calls theirs. The exclusion list survives as a fallback for untagged stacks, now
+matching on the path with any query or fragment stripped. When a tag is expected and no tagged
+frame exists — WebKit routinely produces none — it reports **nothing** rather than guessing.
+
+The reporter's framing was right and is worth keeping: *a wrong line is worse than none,
+because it sends you confidently to the wrong place.*
+
+### `toBeCloseTo`, `toBeGreaterThanOrEqual`, `toBeLessThanOrEqual` in doc tests (#142)
+
+Also from that report. Everything renderer-shaped is floats — intensities, densities, bounding
+boxes — and without `toBeCloseTo` they were writing `Math.round(x * 1e6) / 1e6` at every
+assertion. Jest's semantics exactly, so the habit transfers: `digits` is decimal places and the
+tolerance is half a unit in the last one. All three compose with `.not`.
+
 ## 1.15.0
 
 ### `save-to-source` wrote edits into the wrong fence, silently

package/bin/caddy-install.ts

@@ -38,7 +38,7 @@ import {
   parseArgv,
   resolvePreviewHost,
   resolveSiteConfig,
-} from './resolve-site-config'
+} from './resolve-site-config.ts'
 
 const { has, flag } = parseArgv(process.argv.slice(2), {
   bin: 'tosijs-caddy-install',

package/bin/deploy-preview.ts

@@ -33,12 +33,12 @@ import {
   registerCaddyFragment,
   resolvePreviewHost,
   parseArgv,
-} from './resolve-site-config'
+} from './resolve-site-config.ts'
 import {
   resolveSiteConfig,
   isSafeRemotePath,
   safeRemoteRoots,
-} from './resolve-site-config'
+} from './resolve-site-config.ts'
 
 const { has, flag } = parseArgv(process.argv.slice(2), {
   bin: 'tosijs-deploy',

package/bin/docs.ts

@@ -7,4 +7,11 @@
 //
 // No `/*#` doc block here on purpose: the documented copy lives in the real
 // module, so the doc extractor surfaces it once (avoiding a slug collision).
-export * from '../src/doc-system/site/docs'
+//
+// It must point into dist/, not src/: src/ is not in package.json#files, so the src path
+// resolved only inside this repo and the shim was broken for every consumer from the move
+// (2026-06-14) until 1.15.2. Found by release-doctor's shipped-relative-specifier check.
+// Note the bare `'tosijs-ui/bin/docs'` spelling above does NOT resolve: the exports map's
+// `./*` wildcard sends it to dist/bin/docs.js. Only a file path or `bun bin/docs.ts` reaches
+// this file. See TODO.md.
+export * from '../dist/doc-system/site/docs.js'

package/bin/release-notes.ts

@@ -73,7 +73,7 @@ import {
   lastVersionTag,
 } from '../dist/doc-system/release-notes.js'
 
-import { parseArgv } from './resolve-site-config'
+import { parseArgv } from './resolve-site-config.ts'
 
 // ── CLI ──────────────────────────────────────────────────────────────────────
 

package/bin/tunnel.ts

@@ -39,7 +39,7 @@ import {
   resolveSiteConfig,
   resolveTunnelLocalPort,
   parseArgv,
-} from './resolve-site-config'
+} from './resolve-site-config.ts'
 
 const { has, flag } = parseArgv(process.argv.slice(2), {
   bin: 'tosijs-tunnel',