mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-04 21:17:30 +00:00
* fix(studio): load GSAP core when only a GSAP plugin is on the page The Studio preview checked for GSAP core by matching "gsap" anywhere in a script src, so the MotionPathPlugin it had just injected (served from gsap@x/dist/) counted as core. A composition with a motion path and Studio-edited motion but no GSAP script of its own then got the plugin and no core, and its animations did not run. Detect core by file name (gsap.js, gsap.min.js, or a vendored gsap-<version>.min.js) on any host or path, and inject Studio motion's core before the MotionPathPlugin so the plugin can register onto it. Apply the same core-only check to the sub-composition preview fallback and the missing_gsap_script lint rule. Refs #6205 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * refactor(studio): keep GSAP core detection within the comment budget Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix(studio): load GSAP core ahead of head plugins and only on a real core script Studio motion and sub-composition previews now insert GSAP core before the first GSAP plugin script in the head, so an authored MotionPathPlugin or CustomEase registers on core instead of running first. Core detection keys on a core script (src, inlined marker, license banner or library body), not on usage like gsap.registerPlugin() or gsap.defaults(). The missing_gsap_script lint rule drops the same usage-based and plugin-banner shortcuts. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>