Right now there is an alternative using custom and default slot props, but requires wrapping the component, for example:

<template>
  <NuxtLink to="/someroute" custom #="{ navigate }">
    <v-btn @click="navigate">Link</v-btn>
  </NuxtLink>
</template>

Router-link is available in nuxt right? How does using this instead behave differently?

Router-link is available in nuxt right? How does using this instead behave differently?

Both are there, this PR should be changed to allow render RouterLink and NuxtLink (v2 behavior): https://nuxt.com/docs/api/components/nuxt-link

The linked issue explains the behavior...

Sorry for the confusion:

This PR was about adding NuxtLink:useLink support from Nuxt issue (the releated issue here was mentioned there, but it is not related): Nuxt issue is about adding useLink, Vuetify issue is about rendering RouterLink and/or NuxtLink.

That doesn't really answer my question. NuxtLink supports internal and external links but we already have that with to/href. Afaict the only other difference is prefetching but you haven't implemented that in useLink.

Hey everyone! 👋

I was reviewing this PR and wanted to suggest an improvement to make it more flexible and configurable.

Currently, the PR directly resolves 'NuxtLink', which could cause issues if the component name is changed in the Nuxt config or if it's not globally registered. Instead, we could use Vue’s inject API to dynamically resolve the component name, making it more adaptable.

Proposed Approach:

Use inject to allow dynamic configuration, with 'RouterLink' as the default fallback:

const injectedRouterLinkName = inject<string>('vuetify-router-link', 'RouterLink')
const RouterLink = resolveDynamicComponent(injectedRouterLinkName) as typeof _RouterLink | string

This approach also enables Nuxt users to configure the component name via a plugin while keeping it flexible for other use cases:

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.provide('vuetify-router-link', 'NuxtLink') // Customizable component name
})

This would make the implementation more adaptable to different configurations and user preferences. 🚀