mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-14 18:01:20 +08:00
Miguel Ángel
40dbe06484
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.