vue-class-component VS Vue.js

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.

Vuejs

Vue.js is a big favorite for making websites because it's easy to use and fits in well with other stuff. Many people worldwide are using it, and the community keeps growing.

Vue has a thriving ecosystem with a wide range of third-party libraries and plugins available for extending its functionality. These libraries cover everything from state management to routing, making it easy for developers to find solutions to common problems and enhance their development workflow. As of this writing, Vue has 200k GitHub stars.

6. Vue.js

I have got the privilege of working on Vue 2 couple of months ago and its really amazing framework to work with .

Angular is as little innovative for web frameworks as Firefox-ESR is for browsers. It merely keeps copying features from other frameworks - just many years later. It is a chronically outdated framework that always struggles to keep up with its competitors. It would be ok if those were deliberate design decisions, but if the features get copied some day anyway, what is the point? Why not do it the right way from the start?

For example, this update brings us computed properties, an essential feature for any complex performant web application that was made popular by Vue.js 10 years ago [1]. And now in 2023 we get it in Angular, essentially a confirmation by its devs that its lack has always been a design error.

I also cannot understand the "mature" argument. For example, it took five years for documentation on `` to arrive [2]. This is something I'd expect from the side project of a lone programmer, not an enterprise-level framework.

The only upsides of Angular are its "batteries included" approach and the (debatable) default of RXJS, while the downsides are plenty.

[1] https://github.com/vuejs/vue/tree/218557cdec830a629252f4a9e2...

It's down since months. https://github.com/vuejs/vue/issues/11867

{ "user": "vuejs", "repo": "vue", "url": "https://github.com/vuejs/vue", "stars": 201555, "description": "🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.", "topics": [ "javascript", "framework", "vue", "frontend" ], "label": "repository", "commitCount": 3544 }

Vue.js is a progressive open-source MVVM frontend JavaScript framework that is designed to be implemented incrementally since the core library focuses only on the presentation layer. Nevertheless, this framework is used for building UI (user interfaces) and complex single-page applications with modern tools and libraries to support them. It enables you to take advantage of libraries for client-side routing and state management when you need it.