* feat(cli): align primitive funnel measurement * fix(cli): make primitive claims process-atomic * fix(cli): keep primitive funnel terminals from losing events Terminal funnel events took a durable single-use claim before they were sent, but delivery was the fire-and-forget exit flush: a detached child with no retry and no way to report failure. An unacknowledged send left the claim spent on an event PostHog never received, so that step could never be emitted again. Observed in a real install, where primitive_preview_succeeded was claimed and never arrived. The terminal path now awaits delivery and hands the claim back when the batch is not acknowledged. That trades a permanent loss for a possible duplicate, which is the cheaper failure: every funnel event carries a stable event_id, so duplicates collapse downstream while a loss is unrecoverable. Claims are also no longer spent while telemetry is opted out. Separately, funnel order is now carried by an explicit funnel_step rather than inferred from timestamps. Auth completion and install start are emitted back to back inside one command and land in the same millisecond, so ordering by time resolved them arbitrarily and could report an install beginning before the auth that authorized it.
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