hyperframes preview.
Prerequisites
Build the monorepo first. Every time you change source files, rebuild before testing.Option 1: pnpm link (recommended)
pnpm link --global makes the hyperframes binary in your $PATH point at your local build. It survives across terminal sessions and auto-picks up new builds without re-linking.
hyperframes normally in any directory:
pnpm build the linked binary is already up to date — no re-linking needed.
To restore the published release when you’re done:
Option 2: node alias (no PATH changes)
If you don’t want to touch your global$PATH, add a shell alias or call node directly:
/path/to/hyperframes-oss with your actual monorepo path.
Option 3: npm pack (test the exact published artifact)
Use this when you want to verify what would actually ship in a release, including the bundled studio and templates.Testing the fix branches
When validating a specific bug fix, extract one of the test project archives and run through the scenario:| Bug | Project | Steps |
|---|---|---|
| Audio silent after seek | golden-lyric-video | Play → seek → play again, verify audio |
| Render stuck at 0% | any | Renders tab → Export → watch progress bar |
| Download 404 after restart | any | Complete a render → Ctrl+C → restart → Download |
| Timeline stops early | intro-vid | Play → should reach 0:05, not stop at 0:03 |
| Lottie missing | hyperframe-build-up-demo | Play → rocket visible during 0–2 s |
| Blank thumbnails | any | Compositions sidebar should show previews |
Troubleshooting
Changes not reflected afterpnpm build
The CLI binary is a single bundled file at packages/cli/dist/cli.js. If your change is in @hyperframes/core or another workspace package, make sure pnpm build rebuilt all packages — the CLI bundles its dependencies at build time.
hyperframes still shows the old version / old UI
A globally installed hyperframes package shadows pnpm link. Check which binary is active:
hyperframes preview defaults to port 3002 and auto-increments if it’s taken. Pass --port to use a specific port: