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
TS2322: Type MotionValue<number> is not assignable to type
string | number | CustomValueType | MotionValue<number> | MotionValue<string> | MotionValue<any> | undefined
Type MotionValue<number> is not assignable to type MotionValue<any> with 'exactOptionalPropertyTypes: true'. Consider adding undefined to the types of the target's properties.
Types have separate declarations of a private property current
3. IMPORTANT: Provide a CodeSandbox reproduction of the bug
N/A
4. Steps to reproduce
N/A
5. Expected behavior
No error
6. Video or screenshots
N/A
7. Environment details
"motion": "11.11.17",
The text was updated successfully, but these errors were encountered:
1. Read the FAQs 👇
Read
2. Describe the bug
After migrating from
framer-motion
tomotion
, I can't no more pass MotionValue to a component frommotion/react-m
:3. IMPORTANT: Provide a CodeSandbox reproduction of the bug
N/A
4. Steps to reproduce
N/A
5. Expected behavior
No error
6. Video or screenshots
N/A
7. Environment details
"motion": "11.11.17",
The text was updated successfully, but these errors were encountered: