feat: add unplugin-vue-components and unimport integration

[userquin]

Description

This PR includes:

• unimport presets for Vuetify composables and directives and Vuetify One composables
• unplugin-vue-components resolvers for Vuetify components and directives
• update unimport and unplugin-auto-import to latest versions (3.13.1 and 0.18.3 respectively)
• docs: replace inlined auto import presets for Vuetify and Vuetify One composables
• docs: add Vuetify Directives preset to allow Volar suggest them: right now we need feat(vue): add auto-import directives unplugin/unplugin-auto-import#534 merged and released
• add unbuild to build the new new subpackages exports (node stuff): I have no idea how to configure/call unbuild with custom build.config.mts configuration file, right now using build.config.mts in vuetify package root, should be moved to build folder: should be fixed with this PR feat: add --config to the CLI unjs/unbuild#440 (it should be ported to v2 or update here to use v3-rc version)
• add some jsdocs to Rollup configuration files and extract some constants to its own module: now we have types inside the mjs modules.
• add vuetify/unimport and vuetify/unplugin-vue-components to package exports and typesVersions
• remove auto import logic in vuetify playground: use unplugin-vue-components to auto import components, lab components and directives: reverted since the CI test process hangs (I need to review Vite playground configuration)

We need to add these 2 new integrations somewhere in the docs.

Note

We need to review the lint script, right now I excluded packages/vuetify/src/unplugin from the tsconfig.dist.json file to allow build vuetify.

Note

Maybe we should add a new package or move this PR to another repository.

Tip

• vuetify/unplugin-vue-components: will resolve components and directives: the directives will be missing from the Vue module augmentation and so Volar will not suggest Vuetify directives in the Vue templates. vuetify/unplugin-vue-components won't be able to auto import Vuetify composables.
• vuetify/unimport via unplugin-auto-import: will auto import Vuetify composables and directives and won't be able to auto import Vuetify components. vuetify/unimport will add Vuetify directives in the Vue module augmentation to allow Volar suggest them in the Vue templates (when feat(vue): add auto-import directives unplugin/unplugin-auto-import#534 merged and released).
• vite-plugin-vuetify: same behavior vuetify/unplugin-vue-components. vite-plugin-vuetify adds Vuetify SASS variables support.
• vuetify-nuxt-module: will use vuetify/unimport to auto-import Vuetify composables and directives (requires this PR feat(nuxt,schema): add directives folder nuxt/nuxt#29203 merged and released) and will use Nuxt internal components loader to load Vuetify components (requires this PR feat!: use Nuxt components loader instead custom Vite plugin nuxt-module#276 merged and released). Since it will use vuetify/unimport, Vuetify directives will be suggested by Volar in Vue templates. vuetify-nuxt-module adds Vuetify SASS variables support via custom styles Vite plugin.

Note

• Vue Lazy Hydration will not be handled. Since it is a lower level feature, Vuetify, vuetify/unplugin-vue-components, vuetify/unimport, unplugin-auto-import and vite-plugin-vuetify cannot handle it and current vuetify-nuxt-module will fail to resolve LazyV*** components since it is based on vite-plugin-vuetify to resolve Vuetify components.
• vuetify-nuxt-module will allow to use Vue Lazy Hydration (🤞 ) via Nuxt Delayed Hydration Support and vuetify/unimport preset.
• initial version of Nuxt Delayed Hydration Support is limited, we cannot use it; for example, slots are not provided once component hydrated => FIXED: Daniel Roe sent fix(nuxt): pass slots through to lazy hydrated components PR that will be available in Nuxt 3.17.0, check this repro using lazy-vuetify-btn and lazy-vuetify-calendar (enabled prefixing vuetify components) https://github.com/userquin/vuetify-nuxt-unimport-component-prefix

[KaelWD]

Why are you using a separate build process for this?

[userquin]

We must split client and node builds, I can move it to rollup but I like unbuild.

[userquin]

done:

• added some jsdocs to rollup config files to have auto complettion and suggestions in the ide
• removed unbuild and moved unplugin/*.ts build to Rollup
• fixed also the lint script: added rootDir and custom exclude in tsconfig.check.json

[userquin]

I'm going to split this pr to add jsdocs annotations to rollup config and add hanging-process reporter in vitest configuration.

I didn't check Vitest using Vuetify Vite playground configuration: reverted changes and CI green.

[userquin]

It will be better to add importMap.json and importMap-labs.json to package exports, this change will allow use dynamic import instead resolving vuetify base and reading the file (or just use dynamic import via vuetify/dist/json/importMap.json or vuetify/dist/json/importMap-labs.json).

[KaelWD]

We're using readFile here because node 20 logs a warning for import attributes

[userquin]

This PR will be superseded by another 3 PR:

• move repo to ESM
• fix vuetify types and simplify package exports
• feat(package): add unimport presets and unplugin-vue-components resolvers

[userquin]

New @unvuetify/monorepo repository created and initial packages versions published, we'll have some more Vite/Nuxt utilities in this new repository