TypeScript Errors thrown upon leave transition about motion HOT 6 CLOSED

Hello @pachiraDIG ;

Could you send me a reproduction link please ?

I'm currently using this package on a Nuxt 2.15 project and it is working well. 🤔

from motion.

Hi @Tahul, and thanks for the reply. I was able to reproduce the errors in a code sandbox, here.

from motion.

Thanks, I'll take a look at it soon!

from motion.

Hey @pachiraDIG ;

I did get your example to work just fine, you can take a look at it here:
https://codesandbox.io/s/serene-drake-0y49s

Your typing problem is still alarming but it feels like it belongs to the fact that you used useMotions from data itself, which is not the usage I recommend.

This should be documented better though.

I'll be updating all the dependencies on the package an publishing another version soon.

Please let me know if you still struggle with this problem in your app, will be glad to help you out again. 😄

Could you close this issue once the problem is resolved on your side ?

Thanks 👋

from motion.

Hi @Tahul. Thanks again for your help. 😀

Something I forgot to clarify is that the typescript errors are my biggest problem, as I can't pass validation upon merging to our codebase with these errors persisting. Do you have any suggestions in terms of how that FormButton1 component is put together to be able to solve the typescript errors, specifically?

I noticed your change of using the composition api in a way that allows useMotions to be used in the template without it becoming reactive. Thanks! Am I understanding that correctly?

from motion.

Solved here 🎉

from motion.