[vue3] When is 8.0 releasing?

[ninjabhishek]

It looks like v8 rc was released a long time ago. When is the final version expected?

[Fleeck]

I was wondering the same thing. The next branch looks pretty dead to me, please prove me wrong!

[ninjabhishek]

Agreed. Vue 3 typescript class based project works with 8.0, and working on rc candidate is a security concern in a corporate environment. @ktsn your views?

[ruojianll]

This work is very important for VUE 3.

EDIT:
I set up a repo to do this work in vue3.
https://github.com/facing-dev/vue-facing-decorator

[jaeming]

Agree as well. This is the major blocker for my team in updating a very large codebase to Vue 3. I remember hearing assurances from Vue core devs that the class syntax would not be abandoned in favor of composition api but I'm starting to wonder if this is the case anymore.

[ghiscoding]

Side note which might help pushing this, Vue 3 is now default aka Vue 3 is now released has of Feb 7 🚀

[donggyu04]

@ktsn This feature is very important to me. Do you have any progress or update?

[andyfu6]

@ktsn Why not provide Vue constructor like before?

[nseb]

any replies ?

[pkzOR]

I'm looking for status update of v8 and wondering about it's long term viability. Can anyone provide some insight?

[pkzOR]

I'm looking for status update of v8 and wondering about it's long term viability. Can anyone provide some insight?

To answer my own question, it appears that Vue no longer recommends class-components (https://vuejs.org/guide/extras/composition-api-faq.html#relationship-with-class-api) and so there is little incentive to maintain this.

[nseb]

@pkzOR , Thanks , I just read.
About me , I hate the composition setup that I find it makes maintenance difficult because the code is unreadable. I come from the Java world, I use TS and VueClassComponent on a big project, I find the top balance between ease of development and maintenance.

[ninjabhishek]

Vue 3 ecosystem is messed up right now. The core libraries published by vue is interdependent, and so if one is not released, the others, even if released carry unsecured versions. One example would be https://github.com/vuejs/test-utils/blob/main/package.json where it is an rc version carrying the rc of vue-class-components. And then vue-cli-jest v5 carries v27-rc of vue jest. Vue 3 is not ready for enterprise yet. One scan, and we are under red alert

[ImBoop]

I'm looking for status update of v8 and wondering about it's long term viability. Can anyone provide some insight?

To answer my own question, it appears that Vue no longer recommends class-components (https://vuejs.org/guide/extras/composition-api-faq.html#relationship-with-class-api) and so there is little incentive to maintain this.

That's actually nuts. Their reasoning isn't sound at all, class API is more in line with the direction the web is moving, and is also far easier for developers to use. Angular, Web Components, and even React have first class (no pun intended) support for class based components. Vue randomly deprecating/removing features and having no sound strategy make it hard to justify using it in the future.

[WolfspiritM]

That's actually nuts. Their reasoning isn't sound at all, class API is more in line with the direction the web is moving, and is also far easier for developers to use. Angular, Web Components, and even React have first class (no pun intended) support for class based components. Vue randomly deprecating/removing features and having no sound strategy make it hard to justify using it in the future.

Yep. We also moved away from Vue to Angular and are currently rebuilding our components in Angular cause of that. It's sad but I also don't recommend using Vue anymore cause of decisions like that.