You can load [Vuetify Locale Messages](https://vuetifyjs.com/en/features/internationalization/#getting-started) using the `vuetifyOptions.localeMessages` module configuration option, you don't need to configure a Nuxt Plugin with the `vuetify:before-create` hook, the module will import them for you, it has been declared properly to have better DX.

When `@nuxtjs/i18n` Nuxt module is present, `vuetifyOptions.localeMessages` module configuration option will be ignored.

Using the example in [Vuetify I18n](https://vuetifyjs.com/en/features/internationalization/#getting-started) documentation:

Previous configuration will load and configure `zhHans` and `pl` Vuetify messages.

If you have more messages than the default ones provided by Vuetify, you can add them to the locale messages entry or add them adding a new Nuxt plugin registering them in the `vuetify:before-create` hook (remember to merge the messages).

This module will merge the messages for you, so you don't need to worry about it.

If you want to load your custom messages from a Nuxt Plugin:

This module configures and registers Vuetify using Nuxt plugins via `vuetify:configuration` runtime hook.

`vuetify:configuration` hook is for internal use and not meant to be used by third-party plugins or directly from your application.

This module will expose only the necessary Nuxt plugins to configure Vuetify using the options you've configured in your application:

- [icons](/guide/features/icons/): this Nuxt plugin is always registered, you can write your own Nuxt plugin via `vuetifyOptions.icons.defaultSet = 'custom'` Nuxt configuration option, you have an example using UnoCSS in [Adding a new Vuetify icon set](/guide/features/icons/unocss-preset-icons#adding-a-new-vuetify-icon-set), replace the icons with your custom ones.

- [i18n](/guide/features/i18n): this Nuxt plugin will be only registered when `@nuxtjs/i18n` module is configured.

- [date](/guide/features/date): this Nuxt plugin will be only registered when `vuetifyOptions.date` Nuxt configuration option is configured.

If you need to update the Vuetify configuration before calling `createVuetify` and registering the plugin, you can use the `vuetify:before-create` hook in your Nuxt Plugin:

If you need the Vuetify instance after creating it, you can use the `vuetify:ready` hook in your Nuxt Plugin:

The module supports Vuetify Blueprints, just add it to the `vuetifyOptions.blueprint` module option, but with some limitations:

- `ssr` will be ignored, this flag can be only configured internally by the module via the Nuxt ssr option

- `components` will be ignored, configure them using the `vuetifyOptions.components` module option

- `directives` will be ignored, configure them using the `vuetifyOptions.directives` module option

- `locale` will be ignored, configure it using the `vuetifyOptions.locale` module option

- `date` will be ignored, configure it using the `vuetifyOptions.date` module option

- `icons` will be ignored, configure it using the `vuetifyOptions.icons` module option

- `aliases` only supports defining aliases with [strings](/guide/features/globals/global-components.html#aliasing-global-component), using a component type will result in error (`Cannot start nuxt: Unexpected token '.'`)

The module configures the `transformAssetUrls` from [Vuetify Vite Plugin](https://github.com/vuetifyjs/vuetify-loader/tree/master/packages/vite-plugin#image-loading) to resolve relative asset URLs that are passed to Vuetify components such as `VImg` (e.g. `~/assets/img/some.png`).

You can also add custom entries to the `includeTransformAssetsUrls` module option, for example, to include external components, or you can disable the module option to exclude all entries.

The module will include the following normalizations for each entry in `includeTransformAssetsUrls` module option:

- add kebab and pascal case entries (if missing from the original)

- add kebab and camel case and bind (`:xxx`) attrs entries (if missing from original)

- excluded normalizations on original attrs entries containing `:` (for example `xlink:href`)

You can register Vuetify options using a file, the file path **must** be relative to the root folder.

You can also use it in Nuxt Layers, the module will scan for `vuetify.config` files with the following extensions: `js`, `mjs`, `cjs`, `ts`, `cts` and `mts`.

This module will watch Vuetify configuration files in development and only configuration files outside `node_modules`.

Changing Vuetify configuration in development triggers a full page reload (sometimes 2-3) to invalidate virtual modules, avoiding a server restart. We aim to improve this in future versions.

You can omit `vuetifyOptions`, you only need to add one of the following files, the module will load it for you:

If you want the module to omit loading your configuration file, add `config: false` to your configuration:

Use Vuetify components [that require date functionality](https://vuetifyjs.com/en/features/dates/) installing and configuring one of the [@date-io](https://github.com/dmtrKovalenko/date-io#projects) adapters.

To use Vuetify components [that require date functionality](https://vuetifyjs.com/en/features/dates/):

- install one of the [@date-io](https://github.com/dmtrKovalenko/date-io#projects) adapters (optional)

- configure the date entry in your Vuetify configuration:

If you also have `@nuxtjs/i18n` module installed, `vuetifyOptions.date.locale` and `vuetifyOptions.date.rtl` options will be automatically configured, beware, the configured `locale` entry will be ignored.

If you want to use a custom date adapter, you can configure it using `vuetifyOptions.date.adapter = 'custom'`, and then:

- add a Nuxt Plugin and add the `vuetify:configuration` hook to configure your Vuetify options

- you can import the `virtual:vuetify-date-configuration` module, you will have access to the configuration:

No more Vuetify composables manual imports, auto-import is enabled by default:

You can disable auto-import using `moduleOptions.importComposables: false`.

If you are using another composables that collide with the Vuetify ones, enable `moduleOptions.prefixComposables: true` to prefix them with `V`:

`useRules` composable is available from Vuetify `v3.8.0+`. It is enabled by default if you are using Vuetify `v3.8.0+`.

By default, the module will not register any Vuetify directive. If you need to register some directive, use `vuetifyOptions.directives` module option, it has been declared properly to have better DX.

You can register all the directives or only the ones you need: check the [directives definition](https://github.com/vuetifyjs/nuxt-module/blob/main/src/types.ts#L138-L139).

If you want to ignore some directives, you can use the `moduleOptions.ignoreDirectives` option. The module will configure the Vuetify Vite Plugin to [ignore](https://github.com/vuetifyjs/vuetify-loader/tree/master/packages/vite-plugin#ignoring-components-or-directives) the directives you specify.

Example registering all the Vuetify directives:

Example registering a single Vuetify directive, use singular name or array notation:

Example registering multiple Vuetify directives, use array notation: