Files
hyperframes/scripts/generate-catalog-payloads.ts
Miguel Ángel 406bf316a3 fix(catalog): make component previews answer their variables panel (#3323)
* fix(catalog): make component previews answer their variables panel

Every control on a component's catalog page did nothing. Asking
caption-camera-follow for a violet accent rendered gold, and so did green
and blue, on 166 of the 168 components that declare variables.

A component ships a snippet, which is what the page hands you to paste and
which carries the declaration plus the script that turns a chosen value
into a CSS custom property, and a demo.html which stages and animates it.
The preview is built from the demo, and the demo was authored as a copy of
the snippet rather than a reference to it. The copies drifted until almost
none of them carried the declaration or the reader, so the payload for that
page never contained the word violet at all.

Components come in two shapes, so the repair does too.

123 ship a snippet that registers its own paused timeline. That snippet is
a whole piece, so their preview is now built from it and carries markup,
variables and motion together.

45 are markup plus a commented recipe, where the demo owns the motion.
Those demos now carry the snippet's declaration, reader and var-driven CSS
in the registry itself, written by scripts/catalog/sync-demo-variables.ts.
Nothing is patched in at build time.

A test runs that tool in dry mode and fails when a demo has drifted again,
naming the command that repairs it. It also asserts it inspected more than
a hundred components, because a check that silently matches nothing is how
this rotted in the first place.

Measured by rendering every payload in a real player rather than by reading
markup: payloads declaring their variables go from 2 of 168 to 168 of 168,
previews that animate go from 166 to 167, and nothing that moved stopped
moving. ascii-render-pass and star-rating-fill render a still frame when
built from their snippet, so they keep the demo path as a recorded
exception and stay in the state they were already in.

* refactor(catalog): give the preview pipeline one lookup and one entrypoint guard

Follow-up on the same branch, no behaviour change: 42 tests still pass and
`sync-demo-variables --check` still reports all 168 components clean.

The payload generator and the demo sync had each grown their own copy of
"given a component directory, find the snippet and the demo". Both now call
`componentFiles`, which is the same duplication-by-copying that broke the
previews in the first place.

Both catalog generators also carried a byte-identical 12-line guard for
"only run main() when this file is the entrypoint". That clone was already
in the tree, but nothing had touched both files at once before, so it had
never surfaced. It is now `runAsCommand`, and the sync script's variant of
the same condition is `isEntrypoint`.

The rest is flattening: the layering guards read as a table of conditions
instead of a chain, the reporting splits by what it reports, and the entry
resolution comes out of `buildPayload` rather than being spliced into it.

Also runs the formatter over the demos this branch rewrote. Whitespace only,
and `notes-typing` is the only component demo that renders pre-formatted
text, which this does not touch.
2026-08-18 01:37:46 -04:00

317 lines
12 KiB
TypeScript
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
#!/usr/bin/env tsx
/**
* Generate Catalog Preview Payloads
*
* Writes each catalog item's compiled composition to
* `docs/public/catalog/<type>/<name>.json` so the docs site can mount it in a
* live `<hyperframes-player>` instead of an uploaded MP4.
*
* Why JSON and not the composition HTML itself: the docs host publishes only
* JSON and image files out of `docs/public`. `.html`, `.js` and `.css` are
* dropped from the build with no error, so a preview shipped as an HTML file
* 404s in production while its page still serves. The player takes the
* composition as a `srcdoc` string, so JSON is the delivery format that both
* survives the deploy and matches what the player wants.
*
* Usage:
* npx tsx scripts/generate-catalog-payloads.ts # all items
* npx tsx scripts/generate-catalog-payloads.ts --only data-chart # single item
* npx tsx scripts/generate-catalog-payloads.ts --type block # blocks only
*/
import { readFileSync, writeFileSync, mkdirSync, readdirSync, rmSync } from "node:fs";
import { join, relative, resolve, dirname, extname } from "node:path";
import { fileURLToPath } from "node:url";
import {
discoverItems,
prepareProjectDir,
type CatalogItem,
type ItemKind,
} from "./generate-catalog-previews.js";
import { componentFiles } from "./catalog/component-files.ts";
import { runAsCommand } from "./entrypoint.ts";
import {
snippetOwnsItsMotion,
SNIPPET_PREVIEW_RENDERS_STILL,
} from "./catalog/component-variables.ts";
import {
clearPinnedVariableValues,
externalizeDataUris,
inlineMountedComposition,
HOSTED_EXTENSIONS,
hostItemDirectory,
processAssets,
withBaseHref,
} from "./catalog-payload-assets.ts";
const scriptDir = dirname(fileURLToPath(import.meta.url));
const repoRoot = resolve(scriptDir, "..");
const payloadRoot = resolve(repoRoot, "docs/public/catalog");
/**
* Inlining budget for a single payload. A payload is fetched when the reader
* opens the page, so it competes with the page itself rather than with a video
* they chose to play. Items over budget keep their uploaded MP4.
*
* Measured across the current catalog: 148 asset-free payloads run 3 KB to
* 930 KB (median 11 KB), and the heaviest asset-bearing item inlines to roughly
* 5.8 MB because it embeds a real video. This sits above every item but that
* one, which is the item an MP4 preview actually suits.
*/
const MAX_PAYLOAD_BYTES = Number(process.env.CATALOG_MAX_PAYLOAD_BYTES ?? 3_000_000);
/**
* Compositions that paint DOM into a canvas via `ctx.drawElementImage()`.
*
* That API sits behind `chrome://flags/#canvas-draw-element`, so a reader
* without the flag gets a preview that mounts, plays, and shows an empty
* canvas. The recorded video was captured by a renderer that does have it, so
* it is the only preview these items can honestly show.
*/
function needsCanvasDrawElement(html: string): boolean {
return html.includes("drawElementImage");
}
function typeDir(kind: ItemKind): string {
return kind === "block" ? "blocks" : "components";
}
/**
* Does this item build paths we cannot see?
*
* Two tells. A reference the scan found but could not resolve is one, and a
* manifest that declares assets the scan never matched is the other: the
* texture blocks name their masks in the manifest and then assemble the URL in
* a script, so the files are declared but never written down as a path.
*/
function needsOwnDirectory(item: CatalogItem, unresolved: string[]): boolean {
if (unresolved.length > 0) return true;
try {
const manifest = JSON.parse(
readFileSync(join(item.sourceDir, "registry-item.json"), "utf-8"),
) as { files?: { type?: string }[] };
return (manifest.files ?? []).some((f) => f.type === "hyperframes:asset");
} catch {
return false;
}
}
/** Does the item ship anything the host can serve beside the payload? */
function hostsOwnDirectory(projectDir: string): boolean {
const stack = [projectDir];
while (stack.length > 0) {
const dir = stack.pop() as string;
for (const entry of readdirSync(dir, { withFileTypes: true })) {
if (entry.isSymbolicLink()) continue;
if (entry.isDirectory()) {
stack.push(join(dir, entry.name));
continue;
}
if (HOSTED_EXTENSIONS.has(extname(entry.name).toLowerCase())) return true;
}
}
return false;
}
/** Does the item expose variables a reader is meant to change? */
function declaresVariables(item: CatalogItem): boolean {
try {
const manifest = JSON.parse(
readFileSync(join(item.sourceDir, "registry-item.json"), "utf-8"),
) as { variables?: unknown[] };
return Array.isArray(manifest.variables) && manifest.variables.length > 0;
} catch {
return false;
}
}
/**
* Which file this component's interactive preview is built from.
*
* `snippet` for the ones that register their own timeline: the snippet alone is
* a whole piece, and building from it carries markup, variables and motion
* together. `demo` for the ones that are markup plus a commented recipe, where
* the demo owns the motion. Those demos carry the snippet's variable machinery
* in the registry itself, kept in step by
* `scripts/catalog/sync-demo-variables.ts`, so nothing has to be patched in
* here at build time.
*/
function snippetFileFor(item: CatalogItem): string | null {
if (item.kind !== "component") return null;
return componentFiles(item.sourceDir)?.snippetPath ?? null;
}
function buildsFromSnippet(item: CatalogItem, snippetFile: string): boolean {
return (
snippetOwnsItsMotion(readFileSync(snippetFile, "utf-8")) &&
!SNIPPET_PREVIEW_RENDERS_STILL.has(item.name)
);
}
function previewSource(item: CatalogItem): { mode: "snippet" | "demo"; file: string } | null {
const file = snippetFileFor(item);
if (!file) return null;
return { mode: buildsFromSnippet(item, file) ? "snippet" : "demo", file };
}
/**
* What the preview is built from, and whether that is the component's snippet.
*
* A component whose snippet owns its motion gets its preview built from that
* snippet, so variables and animation arrive together. Everything else keeps
* its authored entry.
*/
function renderEntry(
item: CatalogItem,
interactive: boolean,
): { entry: CatalogItem; fromSnippet: boolean } {
const source = interactive ? previewSource(item) : null;
if (source?.mode !== "snippet") return { entry: item, fromSnippet: false };
const entry = { ...item, entryFile: relative(item.sourceDir, source.file) };
return { entry, fromSnippet: true };
}
async function buildPayload(item: CatalogItem): Promise<"written" | "skipped"> {
const outPath = join(payloadRoot, typeDir(item.kind), `${item.name}.json`);
// An item that stops qualifying has to lose its payload, or the page
// generator keeps finding one on disk and emits a player for a preview this
// run just decided it cannot build.
const dropStalePayload = () => rmSync(outPath, { force: true });
// A composition whose variables are meant to be changed has to reach the
// reader uncompiled, or its values are already resolved into the markup.
const interactive = declaresVariables(item);
const { entry, fromSnippet } = renderEntry(item, interactive);
let projectDir: string;
try {
projectDir = await prepareProjectDir(entry, {
compile: !interactive,
uiFragment: fromSnippet,
});
} catch (err) {
// Some items are a stylesheet and a paragraph of prose — a class you add to
// your own captions, with no standalone scene to show. That is a shape, not
// a breakage, and calling it a failure made every run look wrong. The item
// keeps its recorded video, which is the only honest preview it has.
const message = err instanceof Error ? err.message : String(err);
if (!/no <template> or <body> content to render/.test(message)) throw err;
console.log(` ${item.name}: nothing to render on its own, keeping the recorded video`);
dropStalePayload();
return "skipped";
}
try {
const html = readFileSync(join(projectDir, "index.html"), "utf-8");
if (needsCanvasDrawElement(html)) {
console.log(` ${item.name}: needs canvas drawElement, keeping the recorded video`);
dropStalePayload();
return "skipped";
}
const assetTarget = { dir: join(payloadRoot, "assets"), urlBase: "/public/catalog/assets" };
const {
html: withAssets,
hosted,
inlined,
unresolved,
} = processAssets(html, projectDir, assetTarget);
// Compositions arrive with their fonts already embedded, so this catches
// what never looked like a reference in the first place.
const { html: withShared, externalized } = externalizeDataUris(withAssets, assetTarget);
// Publishing the item's own directory and pointing `<base>` at it is what
// rescues paths a script builds at run time, which no scan can predict.
//
// Only for the items that need it. Serving every item's directory would
// duplicate assets already shared by hash and roughly double what the
// repository carries, to fix a handful of compositions.
const itemUrl = `/public/catalog/items/${item.name}`;
const baseHref =
interactive || needsOwnDirectory(item, unresolved)
? hostItemDirectory(projectDir, join(payloadRoot, "items", item.name), `${itemUrl}/`)
: "";
// An interactive preview keeps its mount, so the component travels inline
// and the demo's own pinned values come off — the reader's choices are what
// should reach it.
const withMount = interactive
? clearPinnedVariableValues(inlineMountedComposition(withShared, projectDir))
: withShared;
const withBase = withBaseHref(withMount, baseHref);
// A reference we could not inline is only fatal when the item's directory is
// not being served either; with a base URL in place the browser can still
// fetch it by its own relative path.
if (unresolved.length > 0 && !hostsOwnDirectory(projectDir)) {
console.log(` ${item.name}: cannot inline ${unresolved.slice(0, 3).join(", ")}`);
dropStalePayload();
return "skipped";
}
const bytes = Buffer.byteLength(withBase, "utf-8");
if (bytes > MAX_PAYLOAD_BYTES) {
console.log(` ${item.name}: ${(bytes / 1e6).toFixed(1)} MB payload, over budget`);
dropStalePayload();
return "skipped";
}
mkdirSync(dirname(outPath), { recursive: true });
writeFileSync(outPath, JSON.stringify({ html: withBase }), "utf-8");
const counts = [
hosted + externalized > 0 ? `${hosted + externalized} hosted` : "",
inlined > 0 ? `${inlined} inlined` : "",
].filter(Boolean);
const assets = counts.length > 0 ? `, ${counts.join(" + ")} asset(s)` : "";
console.log(` ✓ ${item.name}: ${(bytes / 1024).toFixed(0)} KB${assets}`);
return "written";
} finally {
rmSync(projectDir, { recursive: true, force: true });
}
}
function parseArgs(): { only: string | null; type: ItemKind | null } {
const argv = process.argv.slice(2);
const value = (flag: string): string | null => {
const at = argv.indexOf(flag);
return at !== -1 ? (argv[at + 1] ?? null) : null;
};
const type = value("--type");
if (type && type !== "block" && type !== "component") {
console.error('--type must be "block" or "component"');
process.exit(1);
}
return { only: value("--only"), type: (type as ItemKind | null) ?? null };
}
async function main(): Promise<void> {
const { only, type } = parseArgs();
const items = discoverItems(type, only);
console.log(`Building ${items.length} catalog payload(s)...\n`);
let written = 0;
let skipped = 0;
let failed = 0;
for (const item of items) {
try {
const result = await buildPayload(item);
if (result === "written") written += 1;
else skipped += 1;
} catch (err) {
failed += 1;
rmSync(join(payloadRoot, typeDir(item.kind), `${item.name}.json`), { force: true });
console.error(` ✗ ${item.name}: ${err instanceof Error ? err.message : err}`);
}
}
// Skips are the items that keep an uploaded MP4, failures are items that
// could not be built at all. Reporting them apart keeps a breakage from
// reading as a considered fallback.
console.log(`\nDone. ${written} payload(s) written, ${skipped} still on video.`);
if (failed > 0) console.log(`${failed} item(s) failed to build.`);
}
runAsCommand(import.meta.url, main);