Xuanru Li
66baa1eacf
`nearestConstraint` returns the element itself when the element clips, because a clipping box is a constraint candidate. `textOverflowIssues` then reported the same physical defect a second time as `text_box_overflow <sel> inside <same sel>`, so every `clipped_text` arrived as two errors and inflated `errorCount`. The guard is `container === element && containerClips`, not `container === element`: a painted, sized box is also a constraint candidate without clipping anything, and there `clipped_text` cannot speak (it needs `clipsOverflow`). An earlier revision omitted the second condition and silenced a real defect — a painted 200px chip whose text ink ran 520px past its edge reported nothing at all. The new test pins that case; it fails against the over-broad guard and the duplicate test fails against HEAD. Measured over 31 fixtures: 9 changed, all the same shape — the duplicate gone, the `clipped_text` error and `ok: false` kept. Includes four fixtures that are genuine defects wearing `overflow:auto` / `ellipsis` / `line-clamp`; all four still gate. 13 registry examples byte-identical. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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