Building and Previewing Renderer/Playground Changes

The One Command

After changing renderer source, Python source, or playground code:

uv run prefab dev build-docs

This is the only command you should use. It orchestrates the full pipeline with smart caching (only rebuilds what changed). Never run raw npm build commands (npm run build:playground, npm run build:renderer) directly — they skip critical steps.

What the Pipeline Does

1. Renderer build (if TS source changed) — npm run build:renderer builds the

code-split ESM bundle for CDN delivery (the primary renderer artifact)

1. Python bundle generation — serializes all src/prefab_ui/**/*.py into

renderer/src/playground/bundle.json for Pyodide

1. Playground build (if playground source changed) — runs Vite with

VITELOCALPLAYGROUND=1 so the Python bundle is inlined

1. Copy to docs/ — puts built files where prefab playground and

mintlify dev expect them

Note: build-docs builds the CDN renderer. The bundled single-file renderer (airgapped fallback) is built separately via prefab dev build-renderers.

Previewing

# Start the playground (serves from docs/)
uv run prefab playground

# Or start the full docs site
mintlify dev --dir docs

The playground runs on port 5174 by default.

Common Mistakes

"attempted to install wheel before downloading it" — the playground was built without VITELOCALPLAYGROUND=1. This happens when you run npm run build:playground directly instead of prefab dev build-docs. Fix: run the full pipeline.

Playground shows stale Python code — bundle.json is stale. The full pipeline regenerates it; raw npm commands don't.

Renderer changes not visible in deploy previews — deploy previews load chunks from the CDN (@latest), not from the branch. Test renderer changes locally.

Reference

Full build and release details: dev-docs/build-pipeline.md