mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-18 07:50:13 +00:00
* feat(core): runtime element handles for the editing channel The runtime gives each element a numeric handle for one page load and answers two new editing-port requests: `elements-at-point` (the stack under a viewport point) and `describe` (handles to plain-data descriptions). Each description carries the element's stable selector, the source facts Studio resolves to a file, earlier class-selector matches counted per source, attributes, inline styles, text, child handles and its client rect. The stable-selector rule and source-attribute read move to core so Studio and the runtime address elements one way; Studio re-exports them and resolves a description's source file and selector index with its own map. Studio adds `PreviewElement` (a checked description) and client helpers. Every channel read now gives up after the agent probe when the frame's runtime has no editing agent, as the seek wait already did. `computed-styles` accepts custom property names with any case or `_`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(core): per-load element handles and a light elements-at-point reply Handles are now "<load>:<n>" strings, where the load id is random per page load, so a handle from an earlier load reads as null like a removed element. `describe` checks the exact format. `elements-at-point` returns only {handle, tag, rect}; callers describe the one they keep. Descriptions cap each attribute and inline-style value, keep only a `data:` value's header, leave <script> and <style> text out, and say when anything was cut. A handle's entry goes once its element is collected or found disconnected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(core): draw the element-handle load id on first use A render seeds crypto.getRandomValues from virtual time, so drawing the load id when the runtime loads shifted every random value the composition drew after it, and the random-stagger-workers render no longer matched its baseline. The id is now drawn the first time a handle is made, which a render never does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(core): keep a parked element's handle, and cut data: headers only from values A scene the preview parks and puts back keeps its element handles: an entry now goes only once its element is garbage-collected. Text that starts with "data:" is no longer cut to a header; that rule applies to attribute and inline-style values. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@hyperframes/studio
Browser-based composition editor UI for Hyperframes. Provides a visual timeline, code editor, and live preview for building video compositions.
Install
npm install @hyperframes/studio
What it does
The studio is a React application with:
- Visual timeline — drag, resize, and arrange elements on tracks
- Code editor — edit HTML and GSAP scripts with CodeMirror (syntax highlighting, autocomplete)
- Live preview — see changes in real time as you edit
- Composition inspector — view and modify element properties
Development
The studio is embedded in the hyperframes preview command. To develop the studio UI itself:
cd packages/studio
bun run dev # Start Vite dev server
bun run build # Build for production
bun run typecheck # Type-check
Tech stack
- React 19, Zustand 4/5 (state management; development uses Zustand 5)
- CodeMirror 6 (editor)
- Tailwind CSS (styling)
- Vite (bundler)
- Phosphor Icons
Documentation
Full documentation: hyperframes.heygen.com/packages/studio
Related packages
@hyperframes/core— types and parsers used by the editorhyperframes— CLI that serves the studio viahyperframes preview