Files
Miguel Ángel 40dbe06484 fix(cli): add FFmpeg and Chrome preflight check before studio renders
Before this change, hitting "Export" in Studio without FFmpeg installed
or without a Chrome headless shell binary would start the render pipeline
and fail deep inside the producer with opaque errors like `spawn ffmpeg
ENOENT` or `Browser was not found at the configured executablePath`
(23 events/month across users).

Now the render route calls an optional `preflightCheck()` on the adapter
before starting any render. The CLI adapter checks for both FFmpeg
(via `findFFmpeg`) and Chrome (via `findBrowser`), returning a 422 with
an actionable install instruction when either is missing. The Studio
frontend reads the structured error from the response body and displays
it inline in the render queue, so users see exactly what to install
instead of a generic "Server error" message.
2026-05-21 17:16:40 -04:00
..
2026-05-21 12:22:12 -04:00
2026-03-21 22:43:56 -07:00

@hyperframes/studio

Browser-based composition editor UI for Hyperframes. Provides a visual timeline, code editor, and live preview for building video compositions.

Install

npm install @hyperframes/studio

What it does

The studio is a React application with:

  • Visual timeline — drag, resize, and arrange elements on tracks
  • Code editor — edit HTML and GSAP scripts with CodeMirror (syntax highlighting, autocomplete)
  • Live preview — see changes in real time as you edit
  • Composition inspector — view and modify element properties

Development

The studio is embedded in the hyperframes preview command. To develop the studio UI itself:

cd packages/studio
bun run dev        # Start Vite dev server
bun run build      # Build for production
bun run typecheck  # Type-check

Tech stack

  • React 18/19, Zustand (state management)
  • CodeMirror 6 (editor)
  • Tailwind CSS (styling)
  • Vite (bundler)
  • Phosphor Icons

Documentation

Full documentation: hyperframes.heygen.com/packages/studio