Files
Xuanru LiandClaude Opus 5 c0921adf3b feat(check): let a held composition declare itself static
`sweep_static` is hardcoded `error`, exempt from persistence tiering, and gates
the run. It fires whenever the geometry+opacity fingerprint is identical across
every sample — so a held title card or logo lockup had no passing spelling at
all. Measured: a fully lint-clean static card, GSAP timeline registered, paused
and seekable, still failed `check`.

`data-layout-allow-static` on the composition root now demotes the finding to
`info`. It is not suppressed: the claim is the author's and can be wrong, and
dropping the finding produced a confidently green report in which every layout,
occlusion and contrast verdict came from one repeated frame with no trace left.
`info` does not gate even under `--strict` and survives `--json`.

Root-scoped, resolved by the same selector chain the fingerprint itself uses, so
the opt-out and the measurement agree on what "the composition" is. A first
attempt reused `data-no-timeline` and read it document-wide; review showed both
halves were wrong. Its meaning at the engine and lint is per-host "does not
register window.__timelines", not "motionless" — and this repo ships
`css-spinner-render-compat` and `raf-ball-render-compat`, which carry it and DO
animate via CSS keyframes and rAF. Those are exactly the unseekable cases the
guard exists to catch, so that version silenced it where it matters most; a
stray attribute on any child disabled the guard for the whole run as well.

The predicate lives in layout-audit.browser.js beside the fingerprint it must
agree with, so the root-only rule is unit-testable — reverting it to a
document-wide query now fails two tests instead of passing all of them.

Docs updated: the escape-hatch list and the "no way out" paragraph in
lint-validate-inspect.md, a row in data-attributes.md, and cli.mdx.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-26 05:21:55 -07:00
..
2026-07-26 02:01:10 -04:00

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