4 of 6 standards met
Repository: vuejs/vue-class-component. Description: ES / TypeScript decorator for class-style Vue components. Stars: 5779, Forks: 430. Primary language: TypeScript. Languages: TypeScript (62.7%), JavaScript (29.7%), Vue (5.7%), Shell (1.4%), HTML (0.6%). License: MIT. Latest release: v7.2.6 (5y ago). Open PRs: 31, open issues: 70. Last activity: 4mo ago. Community health: 50%. Top contributors: ktsn, yyx990803, dependabot[bot], kaorun343, kuitos, finico, AshtomGVA, briangonzalez, ChristianKienle, decadef20 and others.
Last 12 weeks · 0 commits
Here you can read a post from Evan You @yyx990803 https://github.com/vuejs/vue-next/issues/4744#issuecomment-937369062 I feel like this library is not maintained anymore. Maybe it's time to deprecate it? made sense for Vue 2.x when the TypeScript support was really bad. Currently this library provides no additional benefits, it just modifies the syntax of declaring a component. Additionally almost all users of are using (https://github.com/kaorun343/vue-property-decorator) which also seems abandoned. For Vue 3.x the author of @ktsn introduced a new way of declaring props in a component vuejs/vue-class-component#465 which IMO looks really ugly and most developers will not like it. This creates additional chaos in the Vue ecosystem because now you can use the new way of declaring props for class components or just install and use decorators like it was before. Additionally you can also use normal Options API or Composition API. In conclusion, my suggestion is to deprecate and do not further suggest new developers using it. There is no point to fragment the Vue ecosystem into class components and object components where class components provides no gain over the standard Vue syntax.
has been widely used in our projects. vue-class-setup hopes to get official support and further promote the best practices of Vue class. @ktsn See: https://github.com/fmfe/vue-class-setup !image