Repository maintainer status about motion HOT 6 CLOSED

Hey @BobbieGoede! Sorry for the late response. We wanted to re-write the library to have better support for tree-shaking and maintainability. I was starting on #135 last year to get it off the ground as I was in the same state as you. I was an earlier adopter to Nuxt 3 and really loved the library.

Backstory

Unfortunately @Tahul was experiencing a code burnout in general - maintaining & supporting different libraries at the time. He had a a full time job.

Also not to mention I was having a kid at the end of November last year so the free time I had was completely gone trying to take care of her and support her. Also not to mention helping support UNJS, Clack.cc, VueUse/Motion, my own OS Projects and that's not including my Full-time job 😅. I think I took to much then I could handle. Lack of a better word was over working myself in the first full year in OS and was beginning to feel that same pressure as other maintainers. Especially just doing OS doesn't pay the bills for me which is fine since it's something I love. I just have to pay bills so that means I just have to spend more time on things that can help pay to support my family!

I hope that makes since, but while things are slowly getting better at home and work. I would love to re-vive this project and have additional hands that makes it a lot easier to maintain an OS Project!

But again Taul - wanted to fully re-write the library for better support tree-shaking and SSR which was the goal last year.

Furthermore, I would love to gather a roadmap with a good idea on what we want to do! So that others can help where they can. Again I apologize for the lack of communication on this project.

Thanks,
CP

from motion.

Hey @cpreston321, congrats on becoming a parent 😄 it's totally understandable that providing for your family takes priority! Even though I have primarily been contributing to just one OS project (@nuxtjs/i18n) so far, I can imagine it can get stressful quick when working on several projects at once.

I hope that makes since, but while things are slowly getting better at home and work. I would love to re-vive this project and have additional hands that makes it a lot easier to maintain an OS Project!

But again Taul - wanted to fully re-write the library for better support tree-shaking and SSR which was the goal last year.

I'm glad to hear that you're up for reviving this project! I can see how better tree-shaking and SSR support can be a good goal, but wouldn't it be preferable to work towards this incrementally (if possible)?

Furthermore, I would love to gather a roadmap with a good idea on what we want to do! So that others can help where they can.

That sounds good, I think it would be a good start to triage/label the issues to get an idea of whether most issues are bugs or feature requests (or stale) 😅. I would be happy to go through them sometime but would need permissions to add labels.

I also opened a tiny PR which fixes the failing CI actions (#167), and if you publish a new release this issue (#162) can be closed.

from motion.

Hey @BobbieGoede ;

is there any way I can reach you out on Discord maybe?

thank you so much for your interest in the project, it has just been a bit hard for me to keep an eye here lately.

from motion.

This is one of my favorite libraries within the Nuxt and VueUse ecosystem. Would love to see further support if possible as well. It's just some small fixes away from being amazing!

from motion.

is there any way I can reach you out on Discord maybe?

Hey @Tahul, I'm bobbiegoede on Discord 😄 I'll send you a DM!

from motion.

Now that there's been a new release and some issues have been resolved (and I've been invited to collaborate 💪😂🎉) I'll close this.

I won't always be as active but I'll try my best to help maintain this project and hopefully give you guys some breathing space! 😄

from motion.