Vance Ingalls e4c4d2e15d fix(studio-server): address PR #2097 review feedback on relative-timing resolver ...

Documents the shared-pattern context (3rd copy of "resolve relative
data-start", after runtime startResolver.ts and the SDK's own
getElementTimings) and explains when the raw parseFloat fallback in
resolveStart's else branch can actually fire (a malformed grammar string
with a leading number). Adds a test pinning the "reference target exists
but its own timing is unresolvable" branch, which existing tests didn't
cover (only "target doesn't exist" was tested).

Cross-checked the negative-offset clamp concern raised in review: the
SDK's own resolveReferenceStart (session.ts) also clamps to
Math.max(0, ...), so this stays consistent with its sibling — no code
change needed there.

2026-07-09 11:27:53 -07:00

..

src

fix(studio-server): address PR #2097 review feedback on relative-timing resolver

2026-07-09 11:27:53 -07:00

package.json

chore: release v0.7.45

2026-07-08 22:15:49 -07:00

tsconfig.json

refactor: extract @hyperframes/studio-server from core (#1757)

2026-06-27 01:24:01 -04:00

tsup.config.ts

fix(studio-server): child-scoped patch operations with batch abort (#1908)

2026-07-03 17:53:17 -07:00

vitest.config.ts

refactor: extract @hyperframes/studio-server from core (#1757)

2026-06-27 01:24:01 -04:00