tosijs-ui 1.16.15 → 1.16.17

package/CHANGELOG.md

@@ -1,5 +1,74 @@
 # Changelog
 
+## 1.16.17
+
+- **The pinned tjs-lang is 0.14.0-rc.5; it was 0.13.13.** That is the devDependency this
+  package builds and tests with, and `TJS_VERSION`, which sites without their own copy load
+  from a CDN. What it turns on for `tjs` and `ts` examples on those sites, all of it
+  feature-detected in 1.16.16: examples written as modules run (`export` is removed), a
+  console line shows its own value and offers the JavaScript it became, and a built-in
+  `tjs` example that declares a function gains a **Docs** tab beside its code, generated
+  from its signatures.
+- **What can break, and how to stay where you were.** tjs-lang 0.14 refuses some code that
+  0.13 accepted, with no compatibility switch: `||` in a type (a union is spelled `|`),
+  `unsafe var` and `unsafe eval`, and a `wasm` block that cannot compile, among others. Its
+  [changelog](https://github.com/tonioloewald/tjs-lang/blob/main/CHANGELOG.md) lists them
+  under "what breaks". A `tjs` example using one of those stops compiling on a site that
+  loads tjs-lang from the CDN. To keep the old transpiler, install `tjs-lang@0.13.13` in
+  your project: the build copies the installed tjs-lang next to your pages and the page
+  prefers that copy to the CDN. A site that already installs its own tjs-lang is
+  unaffected.
+- The transpiler bundle a page with `tjs` or `ts` examples downloads is larger: 169 kB to
+  195 kB gzip. `dist/iife.js` is unchanged, and pages without such examples load neither.
+- The peer range is unchanged (`^0.13.1 || ^0.14.0-rc.5`).
+
+## 1.16.16
+
+For tjs-lang's book (GitHub #216 item 3 and #210 item 5), plus one change to `llms.txt`.
+Both tjs-lang items are feature-detected, so nothing changes until your tjs-lang has them.
+
+- **A console line shows its own value, and the JavaScript it became.** A dialect's
+  transform may now return `prelude` and `body` beside `code`: its runtime setup, and what
+  the source itself became. When it does (tjs-lang 0.14.0-rc.5 and later), a line typed at
+  an example's console is evaluated for its own value, so a declaration shows `undefined`
+  where it used to show the setup's last assignment, and a line that needs both the setup
+  and `await` shows what it resolved to. The input also gains a small **JS** button that
+  shows the JavaScript for that line. A transform that returns only `code` behaves as
+  before, with no button.
+- **`tjs` and `ts` examples may be written as modules.** `export` is removed from `tjs` and
+  `ts` examples before they run, by tjs-lang's own parser (`stripExports`, from
+  0.14.0-rc.4), and the build's example check does the same. An example runs as a function
+  body, where `export` is a syntax error, so with an older tjs-lang it fails as it always
+  has. `js` examples are unchanged.
+- **The tjs-lang peer range admits the 0.14 release candidates** (`^0.13.1 || ^0.14.0-rc.5`).
+  It read `^0.14.0`, which excludes every prerelease, so `npm install` refused the one
+  tjs-lang that has these features. Run here with 0.14.0-rc.5 installed: the browser lane
+  on Chromium, and the new tests of both features on all three browsers.
+- **`registerDialect` documents what a transform should return.** `testRunner` has been
+  honoured since 1.16.8 but was not in the type or the docs: a dialect that returns only
+  `code` has its inline tests run from their raw text, with JavaScript's semantics. The
+  `transform` type now names `testRunner`, `prelude` and `body`.
+- **An example re-run while it was still loading could leave its page never finishing its
+  tests.** A run replaced by a newer one (tests turned on, or an edit, while the first run
+  was still awaiting a fetch) went on to run its test block against a preview no longer in
+  the page. A test that waits for something to render then waited for ever and the example
+  stayed marked as running, so the page was reported as not finished after 45 seconds. A
+  replaced run now stops before its tests, and one replaced while its tests are running
+  no longer writes its results over the newer run's. Seen on the data-table page off
+  localhost.
+- **`llms.txt` no longer carries a paragraph about the dev server.** A site with
+  `haltijaDev` set used to tell readers of its `llms.txt` to run `bun start` and drive the
+  page with the `hj` CLI. That file is for whoever consumes the library, and those readers
+  have no repo to run. If you relied on it to brief an agent working in your project, put
+  the same note in your `CLAUDE.md` or `AGENTS.md`.
+
+The tjs-lang this package pins for sites that load it from a CDN is still 0.13.13, which has
+neither feature. A site that serves its own tjs-lang (the installed peer, copied
+same-origin by the build) gets both as soon as that is 0.14.0-rc.5.
+
+`LlmsTxtMeta.haltijaDev` is still accepted and now ignored (deprecated). `dist/iife.js`
+grows by about 0.4 kB gzip.
+
 ## 1.16.15
 
 For projects that build their own docs bundle, from tosijs's upgrade to 1.16.13 (board

package/dist/doc-system/site/check-examples.js

@@ -22,7 +22,7 @@ executed, so they're skipped.
 Build-time only (bun). Never import from browser code.
 */
 import { collectCodeTokens } from '../code-fences.js';
-import { rewriteImports, AsyncFunction, loadTransform, transformAvailable, UnsupportedImportError, } from '../../live-example/code-transform.js';
+import { rewriteImports, AsyncFunction, loadTransform, transformAvailable, UnsupportedImportError, withoutExports, } from '../../live-example/code-transform.js';
 import { isLiveFence } from '../example-policy.js';
 // The default live-example context (matches the IIFE globals the pages provide).
 // A project that sets a custom `context` on its <tosi-doc-system> can pass its
@@ -130,7 +130,9 @@ export async function checkExamples(docs, opts = {}) {
                     // We only need to validate that the source builds, not reproduce tjs
                     // lowering exactly.
                     tsTranspiler ??= new Bun.Transpiler({ loader: 'ts' });
-                    js = tsTranspiler.transformSync(rewritten);
+                    // The page removes `export` from a `ts` example when its tjs-lang can; so does
+                    // this, or a module-style example the page runs would fail the build.
+                    js = await withoutExports(tsTranspiler.transformSync(rewritten));
                 }
                 else if (dialect === 'tjs') {
                     const transform = await loadTransform('tjs');

package/dist/doc-system/site/make-llms-txt.d.ts

@@ -30,14 +30,9 @@ export interface LlmsTxtMeta {
     /** optional framing line(s) under the description */
     tagline?: string;
     /**
-     * Mirrors `SiteConfig.haltijaDev`. When set, `llms.txt` tells an agent it can DRIVE the
-     * running page rather than reason about it from source — which is the single most useful
-     * thing an agent can know about a project it is working on, and was previously discoverable
-     * only by reading the doc-site-system page in full.
-     *
-     * `'tunnel'` also carries that meaning — it is `true` plus a remote path — so the note is
-     * written on truthiness, not on `=== true`. Getting that wrong would silently drop the note
-     * for exactly the projects that enabled the MORE capable mode.
+     * @deprecated Ignored since 1.16.16. It used to add a paragraph about driving the dev
+     * server with the `hj` CLI; `llms.txt` is for whoever consumes the library, so that note
+     * belongs in the project's own agent instructions. Kept so existing callers still compile.
      */
     haltijaDev?: boolean | 'tunnel';
     /**

package/dist/doc-system/site/make-llms-txt.js

@@ -147,22 +147,6 @@ export function generateLlmsTxt(outputPath, meta = {}, corpus) {
             '',
         ]
         : [];
-    /*
-    Only advertise browser control when the project has actually opted in. Telling an agent to
-    drive a page that has no dev channel sends it after a capability that will not answer, and
-    a wrong affordance costs more than a missing one.
-    */
-    const haltijaNote = meta.haltijaDev
-        ? [
-            'Running this project locally (`bun start`), the dev server injects a',
-            'localhost-gated dev channel, so an agent can DRIVE the live page with the `hj`',
-            'CLI — `hj navigate`, `hj eval`, `hj tree` — instead of inferring behaviour from',
-            'source. Injected at serve time only, never in the built output. Note that no',
-            'requestAnimationFrame runs under `hj eval`, and tosijs renders are rAF-driven, so',
-            'use it to inspect STATE; a painted-output check needs a real test lane.',
-            '',
-        ]
-        : [];
     // Only for a corpus-driven index: the legacy scan links to dist/ files, not pages.
     const example = corpus ? markdownExample(corpus, meta) : undefined;
     const markdownNote = corpus && meta.markdownPages !== false
@@ -199,7 +183,6 @@ export function generateLlmsTxt(outputPath, meta = {}, corpus) {
         '',
         ...markdownNote,
         ...liveExampleNote,
-        ...haltijaNote,
         '## Pages',
         '',
     ];

package/dist/doc-system/site/orchestrator.js

@@ -1224,7 +1224,6 @@ export async function buildSite(config, opts = {}) {
                         baseUrl: config.baseUrl,
                         basePath: config.basePath,
                         projectLinks: config.projectLinks,
-                        haltijaDev: config.haltijaDev,
                         markdownPages: config.markdownPages,
                         liveExamples: config.liveExamples,
                     }, corpus);