Repository navigation
[FEATURE] No indication that the FFmpeg engine download is a one-time ~30MB cost #1782
Description
Activity
👋 Thanks for opening an issue, @magic-peach!
Our maintainers will review this shortly 🚀
Before you start working
- 📖 Read the CONTRIBUTING.md guide
- 💬 Wait for a maintainer to assign you the issue before starting work
- 🔍 Search for existing issues to avoid duplicates
For GSSoC'26 contributors
If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:
"I'd like to work on this — contributing under GSSoC'26"
Architecture notes
Reframe is a static Next.js app with
output: "export". Key points:- All video processing uses FFmpeg.wasm (client-side, no server)
headers()innext.config.tswon't work — usevercel.jsoninsteadnot-found.tsxrequirespublic/404.html+vercel.jsonroutes config
Happy contributing! ⭐ Star the repo if you find it useful!
Feature description
ExportOverlay.tsx:132-134shows"Loading video engine: X%"during the first-load download, with no context that this only happens once (per session/until cache eviction) and is a real ~30MB download, not a normal processing step.Problem this solves
First-time users have no idea why the first export takes noticeably longer than expected, or whether something is wrong. This is especially relevant since there's a separate open issue (#181) about implementing actual HTTP/service-worker caching for this download — until that ships, at minimum the messaging should set expectations correctly.
Proposed solution
Add a line under the progress bar on first load only: "One-time download (~30MB) — subsequent exports will be faster."
Alternatives considered
Could be folded into whoever picks up #181, but the messaging fix is valuable independently of whether caching is implemented.