Files
zooqueen 75094e0d60 frames: publish the toolchain as @hanzo/frames
@hanzo/frame is taken by the hero video primitive — one full-bleed video
element — which has held that name on npm since it shipped. This repo is the
video toolchain: a CLI, a renderer, a studio, a player. Plural is what it is,
so the CLI publishes as @hanzo/frames and the workspace packages follow it
(@hanzo/frames-core, @hanzo/frames-engine, and the rest).

The binary stays `frames`, and now actually ships. The manifest mapped it to
bin/frames.mjs while the file on disk was bin/hyperframes.mjs, so a global
install produced no working command.

The paths that name a package to fetch were pointing elsewhere. The update
check read registry.npmjs.org/frames, a different author's package, and the
npm, bun and pnpm installers would have pulled it over the CLI; the render
image installed the upstream hyperframes; scaffolded projects and the docs
pinned the unscoped name. All of them now name @hanzo/frames.
2026-08-13 18:10:14 -07:00

133 lines
2.6 KiB
Markdown

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