-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deconstructing useMotions()
returns undefined
#109
Comments
Same problem, try not to deconstruct it: |
Tested on v. 2.0.0-beta.27 and v. 2.0.0, accessing useMotions() with or without deconstruct is always empty ( equals to empty object ) |
I recently encoutered the same issue. After adding a few console log (or just randomly?) the useMotion started working again but it was not stable, and after reloading and/or restarting nuxt it broke again. I got it working again after downgrading nuxt to 3.4.3 and deleting the |
It looks like this is due to the properties on the object returned by I'll mark this a bug since deconstruction is shown as an example in the documentation, will investigate it later! |
useMotions()
returns undefined
Following the examples from the docs:
https://motion.vueuse.org/directive-usage.html#access-a-v-motion-instance
Note the
custom
from useMotions() isundefined
Tested on v. 2.0.0-beta.27
The text was updated successfully, but these errors were encountered: