From 6d2eb140b5b4758dfe0a486aa8013ce04a30c426 Mon Sep 17 00:00:00 2001 From: BatLeDev Date: Fri, 27 Mar 2026 15:45:24 +0100 Subject: [PATCH] fix(vuetify): separate composable auto-imports from component resolution Previously, autoImports in lib-vuetify mixed composables (from lib-vue) with .vue component default exports. This was incorrect: unplugin-auto-import handles script-level imports only, not template component resolution. The .vue entries had no effect and caused "Cannot optimize dependency" warnings from Vite since esbuild cannot pre-bundle .vue files. autoImports now re-exports lib-vue composables only (backwards-compatible, existing consumers using autoImports keep working unchanged). A new componentsResolver is added for unplugin-vue-components, which properly resolves Df-prefixed components (e.g. or ) to their @data-fair/lib-vuetify/*.vue modules. Also adds TSDoc to autoImports, componentsResolver, and settingsPath. --- packages/vue/vite.ts | 21 ++++++++++-- packages/vuetify/vite.ts | 72 ++++++++++++++++++++++++++++------------ 2 files changed, 70 insertions(+), 23 deletions(-) diff --git a/packages/vue/vite.ts b/packages/vue/vite.ts index 244514e..5c71360 100644 --- a/packages/vue/vite.ts +++ b/packages/vue/vite.ts @@ -1,5 +1,22 @@ -// made for https://github.com/unplugin/unplugin-auto-import - +/** + * Preset for {@link https://github.com/unplugin/unplugin-auto-import unplugin-auto-import}. + * + * Auto-imports Vue, vue-router, vue-i18n built-ins and all data-fair composables + * so they can be used in `