[Question | Feature request] Full blueprint support?

[juanjcardona13]

Currently, the Vuetify module for Nuxt offers partial support for Vuetify Blueprints, but with several limitations, as stated in the documentation. Specifically, the following options are not supported or require manual configuration:

• ssr (controlled internally by the module)
• components
• directives
• locale
• date
• icons
• aliases (only supports defining aliases with strings; using a component type results in an error: "Cannot start nuxt: Unexpected token '."'*)

Since Blueprints in Vuetify are designed to simplify project setup, full support in the Nuxt module would be highly beneficial, removing the need for additional manual configuration.

Requests:

1. Would it be possible to add full Blueprint support in future releases?
2. Are there any technical reasons preventing full compatibility?

Having this functionality would allow developers to fully leverage Blueprints without additional setup.

Thank you for your work and for considering this request! 🚀

[userquin]

The problem is about moving the configuration from client side to server side, we need the configuration to be serializable (it is sent to the client via virtual module, you cannot serialize the components for example, I need to review this).

You can create a Nuxt plugin and move the Blueprints to the plugin using vuetify:before-create hook, I guess something like this should work (keep the rest of the configuration in the nuxt config file or external vuetify config file):

import { defineNuxtPlugin } from '#imports'
import { md1 } from 'vuetify/blueprints'

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.hook('vuetify:before-create', ({ vuetifyOptions }) => {
    // update vuetifyOptions with the Blueprint
     vuetifyOptions.blueprint = md1 
  })
})

[juanjcardona13]

Thanks for your early answer