You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ebe35f2
Browse filesBrowse the repository at this point in the historyBrowse files
Throw an actionable invariant for non-DOM custom component refs
Bailing silently out of renderHTML kept the frame loop alive but left
motion.create() components that don't forward a ref to an element doing
nothing at all, with no indication why.
Throw a "custom-component-ref" invariant at mount instead, pointing at
https://motion.dev/troubleshooting/custom-component-ref. This surfaces
in React with a component stack, so the offending component is named.
The renderHTML bail stays for production, where invariants are no-ops.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
"motion.create() components must forward their ref to a HTML or SVG element. For more information and steps for solving, visit https://motion.dev/troubleshooting/custom-component-ref"
45
+
)
46
+
})
36
47
37
-
awaitnextFrame()
38
-
awaitnextFrame()
48
+
test("mounts without error when the ref resolves to an element",()=>{
0 commit comments