unplugin-vue-components icon indicating copy to clipboard operation
unplugin-vue-components copied to clipboard

📲 On-demand components auto importing for Vue

Results 269 unplugin-vue-components issues
Sort by recently updated
recently updated
newest added

Hi, Thanks to the contributors for making vue components more easy to use! I would very much like to use this plugin in my project, but i unfortunately don't seem...

What about namespace separator? Example: ``` components | - Dialog |---- Dialog.vue |---- Window.vue |---- Header.vue |---- Footer.vue ``` Page.vue ```vue ```

enhancement
pr welcome

Recently I came across a bug. I just realize that the code splitting in vue3 using **defineAsyncComponent** is not working. Link to sample project to reproduce the issue [vue3-vite-lazy-loading](https://github.com/Akash187/vue3-vite-lazy-loading) I...

bug
options api

``` function Hello() { return } -------- ``` vite.config.ts ``` plugins: [ Vue(), vueJsx(), Components({ include: [/\.vue$/, /\.tsx$/], resolvers: [ ElementPlusResolver(), ], }), ] ``` result: - vite build ![image](https://user-images.githubusercontent.com/17466991/135217758-b04bda41-599e-4346-9c5a-e02d9bbb2ce3.png)...

https://github.com/antfu/unplugin-vue-components/blob/242341870d1f602d460947ef63248647dbc3323f/src/core/context.ts#L77 https://github.com/antfu/unplugin-vue-components/blob/242341870d1f602d460947ef63248647dbc3323f/src/core/context.ts#L84 On windows watcher path has '\\' separator and not match already defined paths. That leads naming conflicts warnings

pr welcome

Make `generateDeclaration` flexible (maybe have `options.dts` accept an object?) Otherwise the file is constantly marked as changed if the linter / lint staged configuration changes the semi colon / quote...

### Describe the bug Enabling directives loading in Vue 2.7 project using Vite will cause the following error: [vite] Internal server error: [unplugin-vue-components:directive] Cannot find render function position. Noticed that...

``` //types.ts export const enum Flow { 'START_NODE' = 'START_NODE', } //test.vue impor {Flow} from './types; import { reactive } from 'vue'; const data = reactive({ kind : Flow.START_NODE })...

### Description `Icon` of `ArcoDesign` support config `iconPrefix`, but `ArcoResolver` not supports. this PR add the new option to support config `iconPrefix` for `arco`

Following the "Usage" section in the docs, I tried to use this plugin and spent like half an hour trying to figure out why it's not working. At first glance...