data://tape-mini/a.jsonIn-browser rendering, no server round-trip
The engine, in your tab
This page loads the same wasm request engine the runtime pages use, plus a compiled client-graph package of the tape-explainer example. Edit the data, switch template variants, and the engine re-renders live — the timeline below is the engine’s own per-stage timing map, not an animation.
Honest weight disclosure: the engine wasm is ~21.6 MB (about 3.1 MB compressed in transit) and the client-graph package is ~139 KB, fetched when you start the playground. Nothing else on this site needs them.
engine not loaded — nothing fetched yet
/tape-playground/card.htmlStages and counts come from the engine response’s routeTiming map — the same numbers the runtime records. Load cost (fetch, compile, instantiate) is shown once at start.
hypermake client-graph package --root . --owner !tape-playground --bootstrap index.html --out /tmp/pkg.json hypermake explain public://_hypermake/runtime/client-graphs/!tape-playground.json hypermake affected-by data/tape-mini/a.json