unplugin-vue-components
rfcs
unplugin-vue-components | rfcs | |
---|---|---|
18 | 74 | |
3,526 | 4,832 | |
2.0% | 0.1% | |
7.4 | 2.9 | |
6 days ago | 3 months ago | |
TypeScript | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unplugin-vue-components
- Vue 3 vs Vue 2 so far? What's your opinion? Things I didn't like about Vue 3 compared to Vue 2
-
Saw this on twitter last night ππ
unplugin-vue-components, auto import components in the src/components path.
-
Does anyone uses nvim?
One suggestion I have though to make your life easier is to add the unplugin plugin to your app and then you won't have to list all the components you are importing. https://github.com/antfu/unplugin-vue-components
- How to register all the components in subfolders?
-
Import commonly-used module once, not in each component?
Add in unplugin-vue-components and you cut away a lot of boilerplate import nonsense.
-
Amatuer question - I'm using PrimeVUE to create a UI, do I need to import each control I'm using?
Presumably you're using Vite so you can check out unplugin-vue-components and the Prime Vue resolver. This should enable you to simply use whatever component you want within your template and Vite will auto import it for you without having to explicitly do so yourself.
-
Do I need Quasar CLI If I only need Quasar's components and nothing else ?
I can recommend unplugin-vue-components with the quasar resolver
-
Can I import all components in a particular folder with one "import" statement?
As someone mentioned unplugin-vue-components.
- Jak przejΕΔ z Webpack (Vue CLI) na Vite?
-
Vue 3 - UI Framework for large desktop app (Quasar or element plus + vuetify alpha?)
I'd like to add https://github.com/antfu/unplugin-icons and https://github.com/antfu/unplugin-vue-components.
rfcs
-
Svelte 5: Runes
```
We started experimenting with this ling of thought almost 3 years ago:
- First take (ref sugar), Nov 2020: https://github.com/vuejs/rfcs/pull/228
- Take 2, Aug 2021: https://github.com/vuejs/rfcs/pull/368
- Take 3, Nov 2021: https://github.com/vuejs/rfcs/discussions/369
We provided it as an experimental feature and had a decent number of users trying it out in production. The feedback wasn't great and eventually decided to drop it. https://github.com/vuejs/rfcs/discussions/369#discussioncomm...
- A quick look at the new defineModel in Vue 3.3
-
Vue.js Reactivity System: Ref, reactive, shallowRef, & shallowReactive
This is a personal preference, but I use ref almost all the time. Despite tediously writing the .value to access the refβs value, the Vue team is aware of the problem, and the open RFC - Reactivity Transform, was aiming to solve this issue, however, seems like it was abandoned.
-
This New Vue 3.3 defineModel Macro Will Change The Way You Write Your Co...
To stay updated, follow the RFC at https://github.com/vuejs/rfcs/discussions/503.
-
The Rear-Vue Mirror: My Open-Source Origin Story
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.
- Generic Vue components expected to land in v3.3 (finally!)
-
VUE3 goes back to callbacks instead of events?
Now the $on has been removed, but the event subject is causing some confusion, see: https://github.com/vuejs/rfcs/discussions/397
-
10 Mistakes to Avoid When Starting with Vue 3
The RFC has shown that this feature is very controversial, with lots of implications. Personally, I liked it at first, but now I'm against it.
-
Vue 2 end of life December 2023
Here is the Current language: https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md
-
Should we migrate from Vue2 to Vue3 for the current projects we have or just wait till the community gets stabilized?
Plus, even that there is a real possibility that the controversial Reactivity Transform RFC leads to a Vue 4 version, it is likely to bring just minor breaking changes from Vue 3.
What are some alternatives?
unplugin-auto-import - Auto import APIs on-demand for Vite, Webpack and Rollup
volar - β‘ Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]
unplugin-icons - π€Ή Access thousands of icons as components on-demand universally.
unocss - The instant on-demand atomic CSS engine.
pinia - π Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
pinia-shared-state - π Sync your Pinia state across browser tabs.
unplugin-fonts - Universal Webfont loader - Unfonts - based on https://web.dev/optimize-webfont-loading/
react-18 - Workgroup for React 18 release.
vite-quasar-api - spring boot jpa
vuex - ποΈ Centralized State Management for Vue.js.