vue-class-component VS MathPlayground

This was a good change. Evan has always been extremely good at putting his finger on the pulse of the frontend community. If there's a feature or paradigm that people love that would fit in Vue, Evan will incorporate it. Over the years, Vue has implemented (and sometimes later deprecated) dependency injection, JSX support, custom elements, Angular-style class components, Svelte-style ref sugar, and now Solid-inspired compiler optimizations. They even changed the order of a Vue file to match that of Svelte: first the script, then the template.

That is the whole point. Just check this code. If it was written in a basic vue 2 syntax style it wouldn't be a probrem at all :D So I am looking for a workoround to reuse either a component, or the whole module(page). Some trick which won't require a refactoring of a large app.

The docs are not wrong perse because they distance themself from this package: https://github.com/vuejs/vue-class-component But at the time they recommended this package for best ts experience in vue 2. YOu can see that Evan's account is the second biggest contributor.

Vue(TS) is abandoning vue-class-component, preferring to ask developers to use the Composition API. See https://github.com/vuejs/vue-class-component/issues/569

Due to `vue-class-component` is [deprecated in vue3](https://github.com/vuejs/vue-class-component/issues/569). I built a alternative package to do that with many features.

This topic has come up a few times, but I'm hoping that at some point there can be some official guidance from the Vue team on vue-class-components.

According to the Github commit history, the last commit was on 15 Dec 2020. Also, in this conversation, it's saying this library is not maintained anymore, that's why it doesn't work with Vue 3 at all. I did switch from Vue 2 with class style component to Vue 3 since last May. I also switch from Vuex4 to Pinia since last December. I don't have any big issue regarding pass props through different components or using Pinia. The best way to understand how it works is checking Vue 3 and Pinia official document.

I'm particularly a little salty about the situation of vue-class-component. This is an officially supported vue library that thousands of people use (including myself), and it has been left to die on the vine with regard to Vue3. It has been in the same RC state for over a year, with no communication or support as to what is happening.

3) Previously officially supported projects are being essentially abandoned. Vue Cli has been waiting for V5 for the past year, with no indication of release date, and now is in "maintenance mode". Vue Class Component has similarly been waiting for an update for over a year, and still does not have an official release that supports Vue3.

When I was using Vue2 along with vue-class-component and vue-property-decorator it was easy to synchronize v-models between components simply using @ModelSync(). When Vue 3 came out with its Composition API another way was needed to achieve the same result as if Class Component was used.

Web development was hard, but it was also inherently accessible. You could get started with any editor, run your code in any browser, and share it with anyone on any device, anywhere in the world. I could build content sites or highly dynamic apps, and I could easily prototype new ideas. I was hooked.