tosijs-ui 1.14.1 → 1.14.3

package/CHANGELOG.md

@@ -1,5 +1,72 @@
 # Changelog
 
+## 1.14.3
+
+A single-fix patch cut from `v1.14.2`. Carries no 1.15.0 work.
+
+### tjs-lang 0.13.13 — a quoted test block was executed in the HOST page (#135)
+
+On tjs-lang ≤ 0.13.11, a `test '…' { … }` written inside a template literal or a
+double-quoted string was mistaken for a real test block: the body ran at transpile time and
+the text was **deleted from the output**. Both silent.
+
+That is the bad case for a doc site specifically, because documentation about a language
+quotes the language. `transform()` is called from the component — the **host page** — and its
+output is then injected into the iframe, so anything the transpiler executes at transpile time
+runs outside the sandbox that exists for exactly this. Any tjs example *showing* a test block
+had it deleted from the rendered example and executed in the host page. Upstream lost 52 of 99
+failures in their own conversion gate to it before finding the cause.
+
+Fixed in 0.13.12; this moves to **0.13.13** (latest), verified across all four lanes rather
+than on the release note alone. 0.13.5–0.13.13 also carry the AJS/TJS parser split, a
+prototype-chain lookup fix in the VM, a source-size cap on `Eval`/`SafeFunction`, and further
+literal-blindness fixes.
+
+The pin lives in **two** places by design — `package.json` and `TJS_VERSION` in
+`code-transform.ts`, which governs the CDN bundle a doc site actually loads — and both moved
+together. The peer floor is unchanged at `^0.13.1`: raising it would warn on install for
+people whose own pin is older, and the CDN pin is what fixes the behaviour on the default
+path. **If you install tjs-lang yourself, upgrade to ≥0.13.12** — your copy wins over ours.
+
+Reported by tjs-lang, which was blocked on this while moving its playground onto the doc-site
+system. Released as a patch so nobody waits for 1.15.0 for it.
+
+## 1.14.2
+
+A single-fix patch, cut from `v1.14.1` rather than from `main`, so it carries none of the
+in-progress 1.15.0 work.
+
+### `import 'tosijs-ui/doc-browser'` now actually defines `<tosi-doc-system>` (#158, #159)
+
+**If you are building a doc site with `tosijs-ui/site`, upgrade.** The one import every
+adoption doc tells you to write did not register the doc system.
+
+`doc-browser.ts` is a library module — types, helpers, `createDocBrowser()` — while the element
+lives in `doc-system/doc-system.ts`, which imports *from* doc-browser. The dependency arrow ran
+the wrong way, so that import could never have reached the registrar however it was written.
+
+What let it survive several releases is that it was a **partial** success. The leaf components
+(`tosi-sidenav`, `tosi-example`, …) registered fine, so your bundle looked healthy, your own
+elements worked, pages served 200 — and `<tosi-doc-system>` sat in the markup inert. The
+expensive half was quieter: no doc system means no `window.__docTestResults`, so an entire
+inline doc-test corpus **silently stopped existing**. Not a red suite; a suite reporting
+nothing. Two projects hit this independently, one of them reaching a release candidate first.
+
+`tosijs-ui/doc-browser` now resolves to an entry that imports the registrar and re-exports the
+whole documented API. **No code changes** — the line you already wrote starts working.
+
+A more precise spelling, a named `tosijs-ui/doc-system` export, is coming in a later release.
+**This one keeps working**; it is an addition, not a deprecation.
+
+Two sentences were separately false and are corrected: `import 'tosijs-ui'` does **not** also
+register the doc system. The root barrel deliberately excludes that cluster (#133 — it was 77%
+of the barrel's weight, landing on every app that imported a button), so the root import gives
+you buttons and an undefined doc system. That text shipped in the emitted `.d.ts`, the adoption
+page and the adopter reference.
+
+A test now imports the built entry in a subprocess and fails if the element is undefined.
+Verified by mutation: strip the side-effect import and it goes red.
+
 ## 1.14.1
 
 ### The doc-test gate can tell a dropped page from a passing one

package/dist/doc-browser-entry.d.ts

@@ -0,0 +1,2 @@
+import './doc-system/doc-system.js';
+export * from './doc-browser.js';

package/dist/doc-browser-entry.js

@@ -0,0 +1,28 @@
+/*
+The entry behind `tosijs-ui/doc-browser`.
+
+This exists because that import — the one EVERY adoption doc tells you to write, and the one
+the build's own remediation warning prints when it detects a missing doc system — did not
+define `<tosi-doc-system>`.
+
+`doc-browser.ts` is a library module: types, helpers, and the `createDocBrowser()` factory. The
+custom element lives in `doc-system/doc-system.ts`, which imports FROM `doc-browser.ts`. The
+dependency arrow runs the wrong way, so the documented import could never reach the registrar
+however it was written.
+
+The result was precisely the failure mode the adoption page warns about, and it is disguised by
+being a PARTIAL success: `tosi-sidenav`, `tosi-example` and the other leaf components do
+register, so the bundle looks healthy, pages serve 200, and `<tosi-doc-system>` sits in the
+markup inert. The expensive half is quieter — no doc system means no `window.__docTestResults`,
+so an adopter's entire inline doc-test corpus silently stops existing. The suite does not fail;
+it reports nothing. Two projects hit this independently (#158, #159), one of them reaching a
+release candidate before anyone noticed.
+
+A SEPARATE FILE, not a side-effect import inside `doc-browser.ts`: that would be a genuine
+import cycle (doc-system → doc-browser → doc-system). It would probably work, because
+`doc-system.ts` uses `createDocBrowser` only inside methods — but "probably works, depending on
+evaluation order after your bundler reorders it" is not a thing to put under the one import
+every adopter is told to write. Nothing here depends on evaluation order.
+*/
+import './doc-system/doc-system.js';
+export * from './doc-browser.js';

package/dist/doc-system/site/site-config.d.ts

@@ -85,8 +85,10 @@ export interface SiteConfig {
      * (tosijs-ui#145). The build now warns when it can tell, but the warning is a safety net,
      * not the contract.
      *
-     * Importing the package ROOT (`import 'tosijs-ui'`) also works and registers everything,
-     * but pulls in every component. Prefer the subpaths above.
+     * Importing the package ROOT (`import 'tosijs-ui'`) does **NOT** cover this. The root
+     * barrel deliberately excludes the doc-system cluster (tosijs-ui#133 — it was 77% of the
+     * barrel's weight, landing on every app that imported a button), so it registers your
+     * buttons and leaves `<tosi-doc-system>` undefined. Use the subpaths above.
      *
      * If omitted, pages fall back to `scriptUrl` (tosijs-ui's published iife.js), which
      * already contains the doc system.