-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add Nuxt template #61
base: master
Are you sure you want to change the base?
Conversation
subtitle="Explore available framework Features." | ||
target="_blank" | ||
title="Features" | ||
variant="text" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should using NuxtLink
with custom
attr for this.
Maybe we should add some example about using :to
with some list or button, we've still a draft PR to use NuxtLink
programaticaly.
/cc @KaelWD I talk with some friend about nested tabs using :to
and the problem is the scope. Secondary tabs links shouldn't be reactive, in that case otherwise we will get some errors breaking the navigation.
Top Nav. A and B. Then inside B navigate to some child (Toolbar B) and then navigating to some Tab in A => error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirm I got issues by using tabs links with nested routes.
I resolve effectively by using nuxtlink around tabs links
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the template here, we are using external links, we can use nuxt link or just the link directly in the card.
The problem is about routing inside the app.
The error seems to be a problem with EDIT: adding EDIT: removing the vite vue jsx plugin registration and imports in DON'T INSTALL |
chore: add `@mdi/font` dev dependency chore: add `@mdi/font` css to nuxt css entry when using vuetify vite plugin chore: add `vuetify/styles` to nuxt css entry when using vuetify vite plugin chore: enable auto import when using vuetify vite plugin
chore: don't add `vuetify/styles` when using nuxt module
This PR includes the following templates:
nuxt-base
: Nuxt template for Nuxt v3 and Nuxt v4 compat usingvite-plugin-vuetify
andvuetify-nuxt-module
nuxt-default
: Nuxt template for Nuxt v3 and Nuxt v4 compat usingvite-plugin-vuetify
andvuetify-nuxt-module
nuxt-essentials
: Nuxt template for Nuxt v3 and Nuxt v4 compat usingvite-plugin-vuetify
andvuetify-nuxt-module
(using Nuxt layouts))When using
vite-vuetify-plugin
, the template will include a custom Nuxt module to register some Nuxt stuff (SASS + VuetransformAssetUrls
and SASSmoder-compiler
): the styles plugins is disabled and included a custom one extracted fromvuetify-nuxt-module
(we need SASS variables working when SSR enabled avoiding missing sources).✔️ (fixed) Righ now this PR in draft since I'm getting weird error when starting dev server using both,
vite-plugin-vuetify
andvuetify-nuxt-module
. I'll check if the problem is about enabling Nuxt ESLint (check the error below)./cc @danielroe @johnleider @KaelWD @jacekkarczmarczyk
nuxt-essentials error