ViaandClaude
f3b941f1e3
Fallow flagged the `uncaughtException` arrow at CRAP 30.0 (right at threshold). Extracting the three exit paths — emitCliErrorEvent, reportPostRenderTerminationEvent, exitAfterPostRenderTermination, exitAfterCliFailure — pulls the two `_flushSync?.()` optional-chain branches out of the arrow body and drops cyclomatic to 3. Same shape already used on compileStage in a sibling PR. Behavior preserved: EPIPE → exit(0), renderSucceeded → report + flush + exit(0), default → commandFailed + track + flush + exit(1) for uncaught; renderSucceeded → report + return, default → commandFailed + track for rejection. Windows contactSheet flake: `createContactSheet > writes PNG output` timed out at 20025ms (default ceiling 20000ms) on Windows. Test does milliseconds of real work — the wall-clock overhead is sharp's native binary fork under runner I/O jitter. PR #2492 already tried lightening the test; the flake persists at the default ceiling. Bumping the per-test timeout to 60s absorbs runner jitter without hiding real slowdowns (a genuine sharp regression would blow through 60s just as readily as 20s). Targeted per-test bump, not a global suite bump. Co-Authored-By: Claude <noreply@anthropic.com> — Via
hyperframes
CLI for creating, previewing, and rendering HTML video compositions.
Install
npm install -g hyperframes
Or use directly with npx:
npx hyperframes <command>
Requirements: Node.js >= 22, FFmpeg
Commands
init
Scaffold a new Hyperframes project from a template:
npx hyperframes init my-video
cd my-video
preview
Start the live preview studio in your browser:
npx hyperframes preview
# Studio running at http://localhost:3002
npx hyperframes preview --port 4567
render
Render a composition to MP4. Run from the project directory; the positional
argument is the project directory (not a file), so render the project's
index.html directly, or point at a specific composition file with -c:
npx hyperframes render -o output.mp4
npx hyperframes render -c ./my-composition.html -o output.mp4
lint
Validate your Hyperframes HTML:
npx hyperframes lint ./my-composition
npx hyperframes lint ./my-composition --json # JSON output for CI/tooling
npx hyperframes lint ./my-composition --verbose # Include info-level findings
By default only errors and warnings are shown. Use --verbose to also display informational findings (e.g., external script dependency notices). Use --json for machine-readable output with errorCount, warningCount, infoCount, and a findings array.
compositions
List compositions found in the current project:
npx hyperframes compositions
benchmark
Run rendering benchmarks:
npx hyperframes benchmark ./my-composition.html
doctor
Check your environment for required dependencies (Chrome, FFmpeg, Node.js):
npx hyperframes doctor
browser
Manage the bundled Chrome/Chromium installation:
npx hyperframes browser
info
Print version and environment info:
npx hyperframes info
docs
Open the documentation in your browser:
npx hyperframes docs
upgrade
Check for updates and show upgrade instructions:
npx hyperframes upgrade
npx hyperframes upgrade --check --json # machine-readable for agents
Documentation
Full documentation: hyperframes.heygen.com/packages/cli
Related packages
@hyperframes/core— types, parsers, frame adapters@hyperframes/engine— rendering engine@hyperframes/producer— render pipeline@hyperframes/studio— composition editor UI