Files
hyperframes/scripts/catalog-payload-assets.ts
Miguel ÁngelandMiguel Angel Simon Sierra 1ae2067b8d feat(catalog): put the variables panel back, on payloads (#3199)
* feat(catalog): put the variables panel back, on payloads

The panel drove its preview by loading an .html from docs/public, a type the
host does not publish, so it showed an empty frame in production and was
parked when the catalog was re-landed.

It now mounts the same JSON payload the plain player uses and re-mounts it as
values change, injecting them as window.__hfVariables into the composition head
before any of its scripts run, which is where the runtime reads overrides from.
Doing it in the markup rather than after load is what stops the composition
initialising with the wrong values first.

172 items with variables get the panel back; the playhead carries across a
change so a tweak mid-shot does not jump back to frame zero.

* fix(docs): drop the unused url form and the needless escapes

* fix(docs): the panel cannot reference a binding beside the export

* feat(catalog): make importing an SVG the obvious move

A reader arrives at this control with a shape, not with path data, and the
panel asked for the coordinates first. Import is now the primary action in a
drop target you can see is a drop target, and the raw path sits behind a
disclosure for anyone who wants it.

* feat(cli): let a fruitless catalog search report the gap

An agent that searches by meaning and finds nothing worth installing knows
something we do not: the name of a move the catalog is missing. There was no
way to tell us, so that knowledge was lost at the end of every run.

hyperframes feedback --search-miss "<query>" --wanted "<the move>" records it.
It carries no rating, so it never lands in the rating metric, and it is a
separate deliberate command rather than something catalog --query does on its
own: plain search still sends nothing, which is what the CLI promises.

--rating stops being required at the arg level, since a miss has no rating to
give. The check moved into the run body, where an absent one is now handled
rather than crashing on undefined.

* feat(cli): carry tuned variable values into the install snippet

Someone who tunes a block on its catalog page had no way to keep those values:
the install command was the same one everybody gets, and the tuning stayed on
the page.

hyperframes add <item> --vars '<json>' now prints a mount element carrying
data-variable-values, so the values land where the block is used.

They ride on the host rather than being written into the installed file. That
keeps the composition on disk byte-identical to the registry's, so a later
reinstall can still tell an edit from an update, and it lets two mounts of the
same block carry different values.

* fix(catalog): serve the item's own directory so runtime paths resolve

Some compositions assemble their asset URLs at run time —
"compositions/components/" + texture + ".png" for the texture masks, a font the
compiler pulled into _remote_media — and no scan of the markup can see a string
that does not exist until a script concatenates it. Those items either rendered
black or were dropped to a video that had never been uploaded.

Each item that needs it now has its prepared directory published, and its
payload carries a <base> pointing at it, so any relative path the composition
invents resolves. caption-texture renders its masks again, and
variable-font-flex has a preview at all for the first time: its MP4 and poster
are both 403.

Both layouts are published, because which one a composition asks for differs
per item, and a directory only earns that if it is under 2 MB. The 12 MB
texture sheet keeps the recorded video it already had.

* fix(catalog): let the variables panel actually drive the composition

Every control on the panel was inert. The values reached the composition and
nothing repainted, because the payload had already been compiled: compiling
inlines a mounted component and resolves its variables into the markup and CSS,
so by the time a reader turns a knob there is nothing left to change.

An item that declares variables now ships uncompiled, keeping the mount the
runtime loads at run time, which is the only state where data-variable-values
still means anything. The component travels inline as a data URI rather than a
sibling file, because .html is the one type the docs host will not publish. The
demo's own pinned values come off, so the reader's choices reach the mount
instead of losing to the values the demo picked to show itself off.

Measured on the rendered frame rather than the DOM: green rgb(98,207,144),
blue rgb(6,6,199), violet rgb(177,147,230), and back to green.

docs/public/catalog drops from 48 MB to 35 MB along the way, since an
uncompiled payload carries far less than an inlined one.

* feat(catalog): keep variable changes in the url

A reader who tuned a piece lost it on reload, and had nothing to send anyone.
The values now live in the query string, scoped by composition id so two links
never read each other,and only the ones that differ from the defaults are
written, so changing one knob gives a short URL rather than every variable
spelled out.

replaceState rather than pushState: dragging a slider should not leave a trail
of history entries. An unreadable value is ignored rather than thrown, so a
truncated or hand-edited link opens the piece at its defaults.

* fix(catalog): only rewrite the url when a value actually changed

* refactor(catalog): memoise the declared defaults on their content

* feat(catalog): offer an install command carrying the tuned values

The Install block is generated before anyone touches a knob, so it can only
ever print the plain command. Someone who spent a minute tuning a piece copied
it and got the defaults back.

The panel now carries its own command in the Snippet tab, with --vars holding
exactly the values that differ. An untouched piece still offers the same short
command, so nothing gets noisier for the common case.

* fix(catalog): a piece with nothing to render is a skip, not a failure

caption-blend-difference is a stylesheet and a paragraph of prose — a class you
add to your own captions, with no standalone scene to show. The generator
treated that as a build failure, so every run ended by reporting something
broken when nothing was.

It now reports the shape it is and keeps its recorded video, which is the only
honest preview such an item has. A genuine render failure still throws.

* fix(catalog): restore variables from the url on a cold load

A shared link opened at the defaults. The first render happens on the server,
where there is no window to read the query string from, and React then hydrates
against that markup and never revisits it — so the values only appeared once you
touched a control.

The URL is read again after mount, which is the first moment it exists. The
value is also escaped once now rather than twice: URLSearchParams already
decodes on the way out, and decoding a second time turned an SVG path full of
percent-escapes into something that no longer parsed, besides doubling the
length of every link.

* fix(catalog): mount the preview with the values a link carried

The frame was built from the declared defaults and the shared values were
posted to it afterwards, which is too late for anything the composition reads
once at init: a path arrived after the mark had already been drawn from the
default one, so a link looked right in the panel and wrong on screen.

* feat(catalog): the install command follows the values you tuned

Copying the Install line gave the plain command back, because that block is
generated before anyone touches a knob and had no way to know what changed. The
tuned command only existed in the panel Snippet tab, which is not where anyone
looks for it.

The line now reads the same query string the panel writes, so the two agree
without either component knowing the other exists, and a shared link carries the
right command too. replaceState fires no event, so the panel announces its own
writes.

* fix(catalog): send a text variable to the preview once it is finished

Every other control in the explorer reports a whole value on every event: a
slider at any position is a position, a swatch is a colour. A text field is
not. Typing v3 into a badge posted v first, so the preview remounted and
rendered a composition built from half a word.

The post now waits while a text field has focus and goes out when the edit is
committed, with Enter or by clicking away. The field itself is unchanged and
still tracks every keystroke.

---------

Co-authored-by: Miguel Angel Simon Sierra <miguelangelsi07@gmail.com>
2026-08-10 22:40:01 -04:00

396 lines
15 KiB
TypeScript

/**
* Asset handling for catalog preview payloads.
*
* Kept apart from the payload generator so the reference-matching rules can be
* tested without pulling in the renderer: everything here is pure string and
* file work, and the regex below has already been wrong twice in ways only a
* test catches.
*/
import { createHash } from "node:crypto";
import { existsSync, mkdirSync, readdirSync, readFileSync, statSync, writeFileSync } from "node:fs";
import { extname, join, resolve } from "node:path";
export const MIME_TYPES: Record<string, string> = {
".png": "image/png",
".jpg": "image/jpeg",
".jpeg": "image/jpeg",
".webp": "image/webp",
".gif": "image/gif",
".svg": "image/svg+xml",
".woff2": "font/woff2",
".woff": "font/woff",
".ttf": "font/ttf",
".otf": "font/otf",
".js": "text/javascript",
".mjs": "text/javascript",
".css": "text/css",
".json": "application/json",
".glb": "model/gltf-binary",
".gltf": "model/gltf+json",
".wav": "audio/wav",
".mp3": "audio/mpeg",
".mp4": "video/mp4",
".webm": "video/webm",
};
/**
* Extensions the docs host actually publishes out of `docs/public`, verified by
* fetching one file of each type from a deployed preview.
*
* Anything here is written once and linked. Anything else — `.glb`, `.js`,
* `.css` — is dropped from the deploy with no build error, so it has to travel
* inside the payload as a data URI instead. Getting this set wrong is not a
* build failure, it is a 404 nobody sees until a reader opens the page.
*/
export const HOSTED_EXTENSIONS = new Set([
".png",
".jpg",
".jpeg",
".webp",
".gif",
".svg",
".woff2",
".woff",
".ttf",
".otf",
".wav",
".mp3",
".mp4",
".webm",
]);
/** A reference with any query string or fragment removed. */
function pathPart(ref: string): string {
return ref.split(/[?#]/)[0] ?? ref;
}
/**
* Local files the composition loads from beside itself. A `srcdoc` iframe has
* no base URL of its own, so these would otherwise resolve against the docs
* page and 404.
*
* Two rules stop this over-matching. The attribute pattern requires a
* non-identifier character before `src`, or a shader assigned to `vertSrc`
* reads as a file reference. And a candidate only counts once it carries an
* extension we know, which drops `url(#noise)` filter references, `blob:`
* juggling, and bare CSS keywords.
*/
export function localReferences(html: string): string[] {
const found = new Set<string>();
const patterns = [
/(?<![\w$])(?:src|href)\s*=\s*["']([^"']+)["']/gi,
/url\(\s*["']?([^"')]+)["']?\s*\)/gi,
];
for (const pattern of patterns) {
for (const [, ref] of html.matchAll(pattern)) {
if (!ref) continue;
// `%23` is an encoded `#`: an in-document SVG filter reference, not a file.
if (/^(https?:|data:|blob:|mailto:|#|%23|\/\/)/i.test(ref)) continue;
if (ref.includes("\n")) continue;
if (!MIME_TYPES[extname(pathPart(ref)).toLowerCase()]) continue;
found.add(ref);
}
}
return [...found];
}
/**
* Files a script loads by name, such as `loader.load("models/iphone.glb")`.
*
* These cannot be told apart from ordinary strings by shape alone, so unlike
* the definite references above they are only acted on when the name resolves
* to a real file in the item's own directory, and a miss is ignored rather than
* failing the item. Without this pass a 3D model stayed a relative path, which
* resolves against the docs page inside a `srcdoc` iframe and 404s: the preview
* renders, just with nothing in it.
*/
export function probableReferences(html: string): string[] {
const definite = new Set(localReferences(html));
const found = new Set<string>();
for (const [, ref] of html.matchAll(/["']([^"'\s]+\.[a-z0-9]{2,5})["']/gi)) {
if (!ref || definite.has(ref)) continue;
if (/^(https?:|data:|blob:|mailto:|#|%23|\/\/)/i.test(ref)) continue;
if (!MIME_TYPES[extname(pathPart(ref)).toLowerCase()]) continue;
found.add(ref);
}
return [...found];
}
export interface AssetResult {
html: string;
/** Written once to the shared directory and linked. */
hosted: number;
/** Carried inside the payload because the host will not publish the type. */
inlined: number;
/** References left as they were, so the caller can refuse the payload. */
unresolved: string[];
}
export interface AssetTarget {
/** Directory shared by every item, so one font is stored once. */
dir: string;
/** URL the directory is served from. */
urlBase: string;
}
/**
* Point every local reference at something the browser can fetch.
*
* Assets are content-addressed and shared across items rather than inlined per
* item. The catalog's fonts are the reason: a handful of files were being
* base64'd into a hundred payloads apiece, which cost tens of megabytes in the
* repository to say the same thing over and over. Hashing also means a
* regenerated payload is byte-identical when nothing changed.
*
* Types the host will not publish still travel as data URIs, because a link to
* a file that 404s is worse than a larger payload.
*/
export function processAssets(html: string, projectDir: string, target: AssetTarget): AssetResult {
const root = resolve(projectDir);
let out = html;
let hosted = 0;
let inlined = 0;
const unresolved: string[] = [];
const definite = localReferences(html);
const candidates = [
...definite.map((ref) => ({ ref, strict: true })),
...probableReferences(html).map((ref) => ({ ref, strict: false })),
];
for (const { ref, strict } of candidates) {
const source = resolve(projectDir, pathPart(ref));
// A composition reaching outside its own directory would pull an arbitrary
// file from the build machine into a published payload.
const contained = source === root || source.startsWith(`${root}/`);
if (!contained || !existsSync(source) || !statSync(source).isFile()) {
// A name a script passed around that turned out not to be a file is just
// a string; only a reference we are sure about counts as a broken one.
if (strict) unresolved.push(ref);
continue;
}
const ext = extname(source).toLowerCase();
const mime = MIME_TYPES[ext];
if (!mime) {
unresolved.push(ref);
continue;
}
const bytes = readFileSync(source);
if (HOSTED_EXTENSIONS.has(ext)) {
const name = `${createHash("sha256").update(bytes).digest("hex").slice(0, 16)}${ext}`;
const dest = join(target.dir, name);
if (!existsSync(dest)) {
mkdirSync(target.dir, { recursive: true });
writeFileSync(dest, bytes);
}
out = out.split(ref).join(`${target.urlBase}/${name}`);
hosted += 1;
continue;
}
out = out.split(ref).join(`data:${mime};base64,${bytes.toString("base64")}`);
inlined += 1;
}
return { html: out, hosted, inlined, unresolved };
}
/** `image/png` -> `.png`, for naming a blob that arrives without a filename. */
const EXTENSION_FOR_MIME: Record<string, string> = Object.entries(MIME_TYPES).reduce(
(acc, [ext, mime]) => (acc[mime] ? acc : { ...acc, [mime]: ext }),
{} as Record<string, string>,
);
/**
* Below this, a data URI is cheaper than the request it would cost to fetch.
* Fonts, the reason this exists, are far above it.
*/
const EXTERNALIZE_MIN_BYTES = 4096;
/**
* Pull large data URIs already baked into the composition out into shared files.
*
* Compositions arrive with their fonts embedded, so `processAssets` never sees
* them as references and they survive into the payload untouched. Across the
* catalog that was 53.8 MB of base64, most of it the same few typefaces
* repeated. Hashing gives one copy per distinct file no matter how many items
* embed it.
*/
export function externalizeDataUris(
html: string,
target: AssetTarget,
): { html: string; externalized: number } {
let externalized = 0;
const out = html.replace(
/data:([a-z0-9.+-]+\/[a-z0-9.+-]+);base64,([A-Za-z0-9+/=]+)/gi,
(whole, mime: string, blob: string) => {
const ext = EXTENSION_FOR_MIME[mime.toLowerCase()];
if (!ext || !HOSTED_EXTENSIONS.has(ext)) return whole;
const bytes = Buffer.from(blob, "base64");
if (bytes.length < EXTERNALIZE_MIN_BYTES) return whole;
const name = `${createHash("sha256").update(bytes).digest("hex").slice(0, 16)}${ext}`;
const dest = join(target.dir, name);
if (!existsSync(dest)) {
mkdirSync(target.dir, { recursive: true });
writeFileSync(dest, bytes);
}
externalized += 1;
return `${target.urlBase}/${name}`;
},
);
return { html: out, externalized };
}
/** Copy a directory's publishable files into `destDir`, flattening one level. */
function walkInto(from: string, rel: string, destDir: string, onCopy: () => void): void {
for (const entry of readdirSync(from, { withFileTypes: true })) {
if (entry.isSymbolicLink()) continue;
const childRel = rel ? `${rel}/${entry.name}` : entry.name;
const childFrom = join(from, entry.name);
if (entry.isDirectory()) {
walkInto(childFrom, childRel, destDir, onCopy);
continue;
}
if (!HOSTED_EXTENSIONS.has(extname(entry.name).toLowerCase())) continue;
const to = join(destDir, childRel);
mkdirSync(join(to, ".."), { recursive: true });
writeFileSync(to, readFileSync(childFrom));
onCopy();
}
}
/**
* Publish the item's own directory and hand back a base URL for it.
*
* Some compositions build their paths at run time —
* `"compositions/components/" + texture + ".png"` for the texture masks, a
* downloaded font under `_remote_media/` — and no amount of scanning the markup
* can see a string that does not exist until a script concatenates it. Serving
* the directory and pointing `<base>` at it makes every relative path the
* composition can invent resolve, whether we predicted it or not.
*
* Only publishable types are copied; a composition needing something the host
* drops still falls back to inlining, which is handled by the caller.
*/
/** Publishable bytes an item would add, counted before anything is written. */
function directoryBytes(dir: string): number {
let total = 0;
for (const entry of readdirSync(dir, { withFileTypes: true })) {
if (entry.isSymbolicLink()) continue;
const child = join(dir, entry.name);
if (entry.isDirectory()) {
total += directoryBytes(child);
continue;
}
if (!HOSTED_EXTENSIONS.has(extname(entry.name).toLowerCase())) continue;
total += statSync(child).size;
}
return total;
}
/**
* What an item may add by publishing its own directory.
*
* The texture sheets are the reason: one ships 66 masks, twice over, for 12 MB
* — against a whole catalog that is otherwise around 30 MB. An item over budget
* keeps the recorded video it already had, which is no worse than before.
*/
export const MAX_HOSTED_DIRECTORY_BYTES = 2_000_000;
export function hostItemDirectory(projectDir: string, destDir: string, urlBase: string): string {
if (directoryBytes(projectDir) > MAX_HOSTED_DIRECTORY_BYTES) return "";
let copied = 0;
const walk = (from: string, rel: string): void => {
for (const entry of readdirSync(from, { withFileTypes: true })) {
// Nothing here should ever leave the prepared copy, and a symlink is the
// one entry that could point back out of it.
if (entry.isSymbolicLink()) continue;
const childRel = rel ? `${rel}/${entry.name}` : entry.name;
const childFrom = join(from, entry.name);
if (entry.isDirectory()) {
walk(childFrom, childRel);
continue;
}
if (!HOSTED_EXTENSIONS.has(extname(entry.name).toLowerCase())) continue;
const to = join(destDir, childRel);
mkdirSync(join(to, ".."), { recursive: true });
writeFileSync(to, readFileSync(childFrom));
copied += 1;
}
};
// Both layouts are published. The prepared copy holds each asset twice, once
// as the registry stores it and once at its install path, and which one a
// composition asks for differs per item: the texture masks use the registry
// spelling, the caption textures the install one. Guessing wrong is a 404 at
// run time, so the budget below is what keeps the cost in check instead.
walk(projectDir, "");
// The compiler pulls remote media into `_downloads/` but rewrites references
// as if the document sat inside it, so `_remote_media/x.woff2` has to resolve
// from the item root too. Mirroring rather than moving keeps both spellings
// working, and the files are content-identical either way.
const downloads = join(projectDir, "_downloads");
if (existsSync(downloads) && statSync(downloads).isDirectory()) {
walkInto(downloads, "", destDir, () => (copied += 1));
}
return copied > 0 ? urlBase : "";
}
/**
* Point the document at that base, ahead of anything that could resolve a URL.
*
* A `srcdoc` document has no base of its own, so relative paths resolve against
* the docs page and 404. The tag has to be the first thing in the head: a
* `<base>` only governs what follows it.
*/
export function withBaseHref(html: string, href: string): string {
if (!href) return html;
const tag = `<base href="${href}">`;
if (/<head[^>]*>/i.test(html)) return html.replace(/<head([^>]*)>/i, `<head$1>${tag}`);
if (/<html[^>]*>/i.test(html))
return html.replace(/<html([^>]*)>/i, `<html$1><head>${tag}</head>`);
return `${tag}${html}`;
}
/**
* Turn a mounted sub-composition into one the browser can fetch on its own.
*
* An interactive preview ships uncompiled so its values stay changeable, which
* leaves `data-composition-src` pointing at a sibling `.html`. That is the one
* type the docs host will not publish, so the file is carried inline as a data
* URI instead: the runtime still mounts it at run time, and the values on the
* host still govern it.
*/
export function inlineMountedComposition(html: string, projectDir: string): string {
return html.replace(
/data-composition-src=(["'])([^"']+)\1/gi,
(whole, quote: string, ref: string) => {
if (/^(https?:|data:)/i.test(ref)) return whole;
const source = resolve(projectDir, ref.replace(/^\.\//, "").split(/[?#]/)[0] ?? ref);
if (!source.startsWith(resolve(projectDir)) || !existsSync(source)) return whole;
const encoded = readFileSync(source).toString("base64");
return `data-composition-src=${quote}data:text/html;base64,${encoded}${quote}`;
},
);
}
/**
* Drop the values a demo pinned onto its own mount.
*
* A demo picks striking values to show itself off, and the runtime layers those
* over anything the reader chooses, so every control looked dead. Removing them
* leaves the declared defaults, which is the state the panel starts in.
*/
export function clearPinnedVariableValues(html: string): string {
return html.replace(/\sdata-variable-values=(?:"[^"]*"|'[^']*')/gi, "");
}