Files
Miguel Ángel 90b9a18b70 feat(studio,cli): on-canvas GSAP motion-path editing + agent keyframes surfacing
STUDIO — edit a selected element's GSAP motion path directly on the canvas: a
dashed polyline through its x/y keyframes (or motionPath waypoints) with
draggable diamond nodes, in composition coordinates so it tracks GSAP transforms.
- Drag a node to rewrite its keyframe/waypoint; click to select a keyframe and
  park the playhead on it; double-click empty canvas to author a new motionPath;
  add/remove waypoints inline; right-click a keyframe node for the timeline's
  delete actions (remove keyframe / remove all).
- The overlay spills into the canvas margin without bleeding into the side panels.
- Keyframe add/remove key off the tween-relative percentage the GSAP writer
  expects, so edits from the Design panel, timeline, and motion path all persist
  and refresh consistently. Array-form keyframes (`keyframes: [...]`) are
  removable in both the acorn and recast writers.
- Dragging a GSAP-animated element folds the offset through gsap.set instead of a
  conflicting CSS translate; the drag intercept trusts the live runtime so a
  deleted animation can't be resurrected from a stale parse cache. Gated behind
  the keyframes flag.

CLI — `npx hyperframes keyframes [dir|file]` surfaces every GSAP tween, its
keyframes (with absolute times), and an ASCII motion-path drawing so agents can
read and edit motion as data instead of guessing at raw numbers. `--selector`,
`--json` (machine-readable), filters internal hold markers, draws the path only
for genuine multi-point/2-axis motion. Ships the `hyperframes-keyframes` skill
(surface → read → edit → verify loop).

PRODUCER — esbuild ESM banner also shims `__filename`/`__dirname` so bundled CJS
deps (e.g. wawoff2) don't throw "__dirname is not defined" during render.
2026-06-18 02:50:36 -04:00
..
2026-03-21 22:43:56 -07:00

@hyperframes/core

Types, parsers, generators, compiler, linter, runtime, and frame adapters for the Hyperframes video framework.

Install

npm install @hyperframes/core

Most users don't need to install core directly — the CLI, producer, and studio packages depend on it internally.

What's inside

Module Description
Types TimelineElement, CompositionSpec, Asset, canvas dimensions, defaults
Parsers parseHtml — extract timeline elements from HTML; parseGsapScript — parse GSAP animations
Generators generateHyperframesHtml — produce valid Hyperframes HTML from a composition spec
Compiler compileTimingAttrs — resolve data-start / data-duration into absolute times
Linter lintHyperframeHtml — validate Hyperframes HTML (missing attributes, overlapping tracks, etc.)
Runtime IIFE script injected into the browser — manages seek, media playback, and the window.__hf protocol
Frame Adapters Pluggable animation drivers (GSAP, Lottie, CSS, or custom)

Frame Adapters

A frame adapter tells the engine how to seek your animation to a specific frame:

import { createGSAPFrameAdapter } from "@hyperframes/core";

const adapter = createGSAPFrameAdapter({
  getTimeline: () => gsap.timeline(),
  compositionId: "my-video",
});

Implement FrameAdapter for custom animation runtimes:

import type { FrameAdapter } from "@hyperframes/core";

const myAdapter: FrameAdapter = {
  id: "my-adapter",
  getDurationFrames: () => 300,
  seekFrame: (frame) => {
    /* seek your animation */
  },
};

Parsing and generating HTML

import { parseHtml, generateHyperframesHtml } from "@hyperframes/core";

const { elements, metadata } = parseHtml(htmlString);
const html = generateHyperframesHtml(spec);

Linting

import { lintHyperframeHtml } from "@hyperframes/core/lint";

const result = lintHyperframeHtml(htmlString);
// result.findings: { severity, message, elementId }[]

Documentation

Full documentation: hyperframes.heygen.com/packages/core