fix(date): allow configure i18n when using custom adapter

[mmnoori]

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

[userquin]

If you've a custom adapter the plugin cannot do the work for you, the user should add the corresponding logic: changes in this PR does nothing since the configuration is empty (check the virtual date module here https://github.com/vuetifyjs/nuxt-module/blob/main/src/vite/vuetify-date-configuration-plugin.ts#L34-L38 and the empty code here https://github.com/vuetifyjs/nuxt-module/blob/main/src/vite/vuetify-date-configuration-plugin.ts#L45)

[userquin]

uhmm, looks like the problem is about i18n, right?

[userquin]

shouldn't be

if (!enabled)
    return

?

[mmnoori]

I am using i18n.
i just know when vuetifyOptions.date.adapter is NOT set to 'custom',
configureDate plugin won't change date localization.
I assume your code is right 👍👍👍

[userquin]

@mmnoori can you explain the problem? changing the code with my previous suggestion will fix the problem you're trying to solve?

[AndreyYolkin]

Thanks for the PR, and sorry for the long delay. Closing this one because the approach isn't safe to merge as-is.

The change comments out the whole guard:

// if (adapter === 'custom' || !enabled)
//   return

That guard does two things, and disabling both has side effects:

• !enabled — skips date configuration entirely when the date feature is off. Removing this runs dateConfiguration() unconditionally.
• adapter === 'custom' — the custom-adapter path is intentionally handled separately (you provide the adapter yourself via the vuetify:configuration hook), so the built-in configureDate must not run for it.

The underlying need — getting i18n locales applied when using a custom date adapter — is legitimate, but it needs a targeted fix (e.g. still applying the i18n locale map for the custom path without running the rest of the built-in configuration), not removing the guard wholesale. Note also the diff targets the pre-monorepo path (src/runtime/plugins/date.ts, now under packages/vuetify-nuxt-module/).

This whole date/config layer is being reworked in the v2 rewrite (statically-analysable vuetify.config.ts, no Vite plugins — see userquin/vuetify-nuxt-module-nuxt-v4), where custom-adapter + i18n is reconsidered. If you still hit this on the current release, please open an issue with a minimal reproduction and we'll track it. Thanks again! 🙏