vuetifyjs/vuetify

[Feature Request] Support nuxt prop for Vuetify 3 on Routable components

Open

#17490 opened on May 29, 2023

View on GitHub
 (11 comments) (16 reactions) (1 assignee)TypeScript (40,995 stars) (7,139 forks)batch import
C: VBtnNUXTT: featurehelp wanted

Description

Problem to solve

In Vuetify2 adding the nuxt to a routable component (e.g. v-btn or v-card) produced a nuxt-link if to prop or href prop was passed. In Vuetify 3 the nuxt prop does no longer exist.

Proposed solution

Without nuxt prop: <v-btn href="https://vuetifyjs.com"/> => <a href="https://vuetifyjs.com"/> <v-btn to="/vuetify"/> => <router-link to="/vuetify"/> <v-btn /> => <button /> (No href or to)

With nuxt prop: <v-btn nuxt href="https://vuetifyjs.com"/> => <nuxt-link href="https://vuetifyjs.com"/> <v-btn nuxt to="/vuetify"/> => <nuxt-link to="/vuetify"/> <v-btn nuxt /> => <button /> (No href or to)

NOTE: nuxt-link can now handle internal (to) and external (href) links: https://nuxt.com/docs/api/components/nuxt-link

Contributor guide

Tech stack
typescriptvuenuxt
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Vue componentsFamiliarity with Vuetify's routable componentsUnderstanding of Nuxt Link
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
The feature involves adding a `nuxt` prop to routable components like VBtn and VCard in Vuetify 3. The main files to inspect are likely in the packages/vuetify/src/components directory for each component, and possibly a shared mixin or composable for routable behavior (e.g., useRoutable). The implementation should mimic the Vuetify 2 approach but adapted for Vuetify 3's composition API. Since there is one assignee, check if there is a related branch or draft PR. The proposed behavior is clear: when `nuxt` is true, render a `<nuxt link>` instead of `<a>` or `<router link>`. Test files should also be updated accordingly. Review the existing Vuetify 3 code for similar prop handling patterns.