Files
hyperframes/packages/cli/README.md
Miguel Ángel ab129023de docs(cli): fix render examples that pass a file as the project dir [P2] (#1974)
* docs(cli): fix render examples that pass a file as the project dir

The render command's positional argument is the project directory (default
"."), resolved via resolveProjectOrThrow; a specific composition file is
passed with -c/--composition. Several docs showed `hyperframes render
index.html` / `render ./my-composition.html`, which treats the HTML file as
the project dir and fails with "Not a directory". Correct the guide and the
cli README to render the project's index.html directly (or point at a file
with -c).

* docs: fix render index.html example in the Open Design guide too (R1)

R1 flagged that open-design-hyperframes.md carried the identical
`npx hyperframes render index.html` example this PR fixes in the Claude
guide — same failure vector ("Not a directory" for a file positional).
Corrected to `npx hyperframes render` run from the project directory.
2026-07-08 15:53:17 -04:00

131 lines
2.5 KiB
Markdown

# hyperframes
CLI for creating, previewing, and rendering HTML video compositions.
## Install
```bash
npm install -g hyperframes
```
Or use directly with npx:
```bash
npx hyperframes <command>
```
**Requirements:** Node.js >= 22, FFmpeg
## Commands
### `init`
Scaffold a new Hyperframes project from a template:
```bash
npx hyperframes init my-video
cd my-video
```
### `preview`
Start the live preview studio in your browser:
```bash
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`:
```bash
npx hyperframes render -o output.mp4
npx hyperframes render -c ./my-composition.html -o output.mp4
```
### `lint`
Validate your Hyperframes HTML:
```bash
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:
```bash
npx hyperframes compositions
```
### `benchmark`
Run rendering benchmarks:
```bash
npx hyperframes benchmark ./my-composition.html
```
### `doctor`
Check your environment for required dependencies (Chrome, FFmpeg, Node.js):
```bash
npx hyperframes doctor
```
### `browser`
Manage the bundled Chrome/Chromium installation:
```bash
npx hyperframes browser
```
### `info`
Print version and environment info:
```bash
npx hyperframes info
```
### `docs`
Open the documentation in your browser:
```bash
npx hyperframes docs
```
### `upgrade`
Check for updates and show upgrade instructions:
```bash
npx hyperframes upgrade
npx hyperframes upgrade --check --json # machine-readable for agents
```
## Documentation
Full documentation: [hyperframes.heygen.com/packages/cli](https://hyperframes.heygen.com/packages/cli)
## Related packages
- [`@hyperframes/core`](../core) — types, parsers, frame adapters
- [`@hyperframes/engine`](../engine) — rendering engine
- [`@hyperframes/producer`](../producer) — render pipeline
- [`@hyperframes/studio`](../studio) — composition editor UI