\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[3019,3022,3025],{"name":3020,"color":3021},"bug","d73a4a",{"name":3023,"color":3024},"v3","49DCB8",{"name":3026,"color":3027},"triage","ffffff",3972,"nuxt","ui","open","Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.77655005,{"description":3037,"labels":3038,"number":3042,"owner":3029,"repository":3043,"state":3044,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-vy6psx\n\n### Describe the bug\n\n```\r\nError: [vitest] Cannot mock \"vue-router\" because it is already loaded by \"virtual:nuxt:/home/projects/github-vy6psx/.nuxt/vue-router-stub.mjs\", \"virtual:nuxt:/home/projects/github-vy6psx/.nuxt/pages.mjs\".\r\n\r\nPlease, remove the import if you want static imports to be mocked, or clear module cache by calling \"vi.resetModules()\" before mocking if you are going to import the file again. See: https://vitest.dev/guide/common-errors.html#cannot-mock-mocked-file-js-because-it-is-already-loaded\r\n```\r\n\r\nI get this error message whenever I try to mock `vue-router` after upgrading to `3.9.0`. \r\nBefore the merge of `nuxt-vitest` and `@nuxt/text-utils`, the mock worked fine.\r\nI've tried to `vi.resetModules()` and other alike functions, but none of them have helped.\r\n\r\nAdditionally, if `@nuxt/test-utils/module` is present in `nuxt.config.ts` modules, `npm run dev` throws the following error:\r\n```\r\nThis module cannot be imported in the Vue part of your app. [importing @nuxt/test-utils/runtime from pages/__tests__/index.spec.ts]\r\n```\n\n### Additional context\n\nTests can be ran with `npm run test`.\r\n`vi.mock()` is located in `pages/__tests__/index.spec.ts`.\n\n### Logs\n\n_No response_",[3039],{"name":3040,"color":3041},"pending triage","5D08F5",734,"test-utils","closed","vue-router mock","2024-09-23T14:14:32Z","https://github.com/nuxt/test-utils/issues/734",0.7213736,{"description":3050,"labels":3051,"number":3056,"owner":3029,"repository":3030,"state":3044,"title":3057,"updated_at":3058,"url":3059,"score":3060},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nAdd `code` to `defineLocale`, it comes in handy in several components:\n\n* https://www.radix-vue.com/components/number-field.html\n* https://www.radix-vue.com/components/calendar.html\n\nYou need to pass the `locale` property there, you can get it from `defineLocale`\n\n### Additional context\n\n_No response_",[3052,3055],{"name":3053,"color":3054},"enhancement","a2eeef",{"name":3023,"color":3024},2610,"Provide `code` on `defineLocale`","2024-11-12T11:57:53Z","https://github.com/nuxt/ui/issues/2610",0.73700994,{"description":3062,"labels":3063,"number":3070,"owner":3029,"repository":3029,"state":3044,"title":3071,"updated_at":3072,"url":3073,"score":3074},"Hi,\r\n\r\nI noticed that the colorscheme of the code block in the documents of modules doesn't display well in light mode.\r\n\r\nFor example, in [@nuxt/tailwindcss](https://nuxt.com/modules/tailwindcss),\r\n\r\nThe color of the code is the same as the background, for example:\r\n\r\nIn light mode, I can't see any code but comments\r\n\r\n\r\nHowever, in dark mode, it works well\r\n\r\n\r\nThe braces in the code block have a similar issue as well, \r\n\r\nIn light mode, all the braces disappear:\r\n\r\n\r\nCompared with dark mode:\r\n\r\n",[3064,3067],{"name":3065,"color":3066},"documentation","5319e7",{"name":3068,"color":3069},"3.x","29bc7f",15501,"Colorscheme of code blocks in light mode seems unclear","2023-02-15T13:09:14Z","https://github.com/nuxt/nuxt/issues/15501",0.74425805,{"description":3076,"labels":3077,"number":3081,"owner":3029,"repository":3082,"state":3044,"title":3083,"updated_at":3084,"url":3085,"score":3086},"Hi! I've got a misterious problem with nuxt/fonts\nSometimes when deploy I get this kind of error (5 times out of 15 deploys)\n\nThat's not a versel bug, I've tried to run locally `npm run build` about 20 itmes and 5 of them ended up with the same error. \n\nMy configuration:\n\n `\"@nuxt/fonts\": \"0.10.2\"`\n`\"nuxt\": \"3.13.2\",`\n ```export default defineNuxtConfig({\n components: [\n {\n path: \"~/components\",\n global: true,\n },\n ],\n\n devtools: { enabled: false },\n\n css: [\"~/assets/styles/_global.scss\"],\n\n modules: [\n \"@nuxt/fonts\",\n \"nuxt-icons\",\n \"@nuxt/eslint\",\n \"nuxt-quasar-ui\",\n \"@pinia/nuxt\",\n \"@nuxtjs/device\",\n \"@nuxt/image\",\n \"@nuxtjs/seo\",\n \"@nuxtjs/robots\",\n \"nuxt-schema-org\",\n \"nuxt-link-checker\",\n \"@nuxtjs/sitemap\",\n \"nuxt-seo-experiments\",\n \"@nuxtjs/i18n\",\n \"@nuxt/scripts\",\n ],\n\n plugins: [\n \"~/plugins/rest-api.js\",\n { src: \"~/plugins/sentry.ts\", mode: \"client\" },\n { src: \"~/plugins/error-handler.ts\", mode: \"client\" },\n { src: \"~/plugins/image-error.ts\", mode: \"client\" },\n ],\n\n // scripts\n $production: {\n },\n\n $development: {\n },\n\n //SEO\n sitemap: {\n enabled: true,\n urls: async () => await getSiteMap(),\n defaults: {\n changefreq: \"daily\",\n priority: 1,\n lastmod: new Date(),\n },\n },\n robots: {\n enabled: true,\n disallow: [\"/admin\", \"/ui-kit\", \"/profile\", \"/third-party-auth\"],\n allow: \"/\",\n },\n ogImage: {\n enabled: false,\n },\n schemaOrg: {\n enabled: true,\n identity: {\n },\n defaults: false,\n reactive: true,\n },\n seo: {\n automaticDefaults: false,\n fallbackTitle: false,\n },\n linkChecker: {\n enabled: true,\n },\n seoExperiments: {\n enabled: true,\n },\n\n site: {\n\n },\n\n app: {\n head: {\n },\n },\n //SEO\n\n //images\n image: {\n format: [\"webp\", \"png\", \"svg\"],\n },\n //images\n\n //langs\n i18n: {\n legacy: false,\n locales: [\n {\n code: \"en\",\n name: \"English\",\n iso: \"en-US\",\n file: \"en.json\",\n },\n {\n code: \"de\",\n name: \"Deutsch\",\n iso: \"de-DE\",\n file: \"de.json\",\n },\n ],\n messages: {\n en: {},\n },\n defaultLocale: \"en\",\n strategy: \"prefix_except_default\",\n lazy: true,\n langDir: \"locales/\",\n detectBrowserLanguage: {\n useCookie: true,\n cookieKey: \"i18n_redirected\",\n alwaysRedirect: true,\n fallbackLocale: \"en\",\n },\n },\n //langs\n\n //vite\n vite: {\n css: {\n preprocessorOptions: {\n scss: {\n additionalData: '@use \"~/assets/styles/variables/_mixins.scss\" as *;',\n },\n },\n },\n build: {\n sourcemap: true,\n rollupOptions: {\n output: {\n // manualChunks: undefined,\n },\n },\n // cssCodeSplit: false,\n },\n\n plugins: [\n sentryVitePlugin({\n }),\n ],\n },\n //vite\n\n //ui\n quasar: {\n lang: \"ru\",\n plugins: [\"Dialog\", \"Notify\", \"Loading\", \"AppVisibility\"],\n },\n //ui\n\n //env\n runtimeConfig: {\n devtools: {\n enabled: true,\n },\n public: {\n },\n },\n //env\n\n //nitro\n nitro: {\n prerender: {\n // crawlLinks: true,\n routes: [\"/sitemap.xml\", \"/robots.txt\"],\n },\n compressPublicAssets: true,\n },\n //nitro\n\n //prerender\n routeRules: {\n },\n //prerender\n\n router: {\n options: {\n scrollBehaviorType: \"smooth\",\n },\n },\n\n //build\n build: {\n analyze: true,\n },\n\n //build\n\n //hooks\n hooks: {\n // \"build:before\": () => {\n // console.log(\"Running ESLint...\");\n // try {\n // execSync(\"pnpm run lint\", { stdio: \"inherit\" });\n // } catch (error) {\n // console.error(\"ESLint found issues\");\n // }\n // },\n },\n //hooks\n\n //other\n typescript: {\n strict: true,\n },\n ssr: false,\n compatibilityDate: \"2024-11-10\",\n //other\n});\n```\n----------\n```\n.dm-sans {\n font-family: \"DM Sans\", sans-serif;\n font-optical-sizing: auto;\n font-weight: normal;\n font-style: normal;\n}\n\n@font-face {\n font-family: \"Cabinet Grotesk\";\n src: url(\"~/assets/fonts/CabinetGrotesk-Bold.ttf\") format(\"truetype\");\n font-weight: 700;\n}\n\n@font-face {\n font-family: \"Cabinet Grotesk\";\n src: url(\"~/assets/fonts/CabinetGrotesk-Regular.ttf\") format(\"truetype\");\n font-weight: 400;\n}\n@font-face {\n font-family: \"DM Sans\";\n src: url(\"~/assets/fonts/DMSans-Bold.ttf\") format(\"truetype\");\n font-weight: 700;\n}\n\n@font-face {\n font-family: \"DM Sans\";\n src: url(\"~/assets/fonts/DMSans-Regular.ttf\") format(\"truetype\");\n font-weight: 400;\n}\n\n.cabinet-grotesk {\n font-family: \"Cabinet Grotesk\", sans-serif;\n font-optical-sizing: auto;\n font-weight: normal;\n font-style: normal;\n}\n```\n\nIs there any one with the similar problem? \n\n",[3078],{"name":3079,"color":3080},"duplicate","cfd3d7",408,"fonts","Family injection fetch failed","2024-12-05T02:26:06Z","https://github.com/nuxt/fonts/issues/408",0.7482923,{"description":3088,"labels":3089,"number":3091,"owner":3029,"repository":3030,"state":3044,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Description\n\nWhen using a Table component, it would be a cool feature to allow the items to be modified in place and an event emitted. There arent really many good solutions for this in Vue ecosystem, that I know of. \n\n### Additional context\n\n_No response_",[3090],{"name":3053,"color":3054},2168,"Make an inplace editable table","2024-09-11T14:14:15Z","https://github.com/nuxt/ui/issues/2168",0.7490823,{"description":3097,"labels":3098,"number":3103,"owner":3029,"repository":3030,"state":3044,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\r\n\r\n- \"@nuxt/ui\": \"^2.18.6\",\r\n- \"nuxt\": \"^3.13.2\",\r\n- \"vue\": \"^3.5.10\",\r\n\r\n### Version\r\n\r\nv2.18.6\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n### Description\r\n\r\nHello,\r\n\r\nI'm having a important nuxt ui mono repo project and I'm encountering problems with nuxt/ui since version 6.12.0 of @nuxtjs/tailwindcss. \r\n\r\nI was forced to stay in an old version of nuxt/ui to don't have the problem : \r\n\r\n```\r\n \"pnpm\": {\r\n \"overrides\": {\r\n \"@nuxtjs/tailwindcss\": \"6.11.4\",\r\n \"@nuxt/ui\": \"2.15.2\"\r\n }\r\n },\r\n```\r\n\r\n# What happens ? \r\n\r\nAt first launch, css classes used in nuxt ui components are not correctly taken into account. \r\nIt's necessary to restart a second time the app to have the correct display\r\n\r\nThe bug is present since the version 6.12.0 of nuxtjs/tailwindcss. Maybe some effect of the First Class HMR.\r\n\r\n## Step to reproduce \r\n\r\nThe code at the following link is a minimal reproduction of my project structure : https://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n- From the root project path, launch the following command : \r\n\r\n```bash\r\n# Clear the build \r\n./scripts/CleanProject.bash\r\n\r\n# Install and prepare \r\npnpm i; pnpm run dev:prepare\r\n\r\n# Launch the app\r\ncd apps/mmi-order-front-office\r\npnpm run dev\r\n```\r\n\r\n**The tailwind classes used in apps and modules are correctly displayed but the tailwind classes defined in the nuxt-ui components are not taken into account.**\r\n\r\n\r\n\r\n- Stop and restart the server\r\n\r\n```bash\r\npnpm run dev\r\n```\r\n\r\n**All tailwind classes are correctly taken into account.**\r\n\r\n\r\n\r\n\r\n\r\nThe problem is present too when building the prod version with **pnpm run build**\r\n\r\n\r\nThe problem seems to happens when using nuxt ui in a nuxt module. Please, have you any ideas, to solve this problem. \r\n\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3099,3100],{"name":3020,"color":3021},{"name":3101,"color":3102},"upstream","78bddb",2282,"Since Tailwind First Class HMR, nuxt-ui components css classes not taken into account at first launch","2024-10-18T09:16:15Z","https://github.com/nuxt/ui/issues/2282",0.75009656,{"description":3109,"labels":3110,"number":3115,"owner":3029,"repository":3082,"state":3044,"title":3116,"updated_at":3117,"url":3118,"score":3119},"## Description\n\nUsing nuxt fonts to set different fonts for specific CSS classes works perfectly for single-level classes, but when trying to apply a font to nested CSS classes, it does not load as expected.\n\nFor example, Lato works fine for `.lato`, but Nunito fails to apply in nested elements like `.nunito p`:\n\n```vue\n\u003Ctemplate>\n \u003Cdiv class=\"lato\">\n 'Lato works!'\n\n \u003Cdiv class=\"nunito\">\n \u003Cp>'Nunito does not work :('\u003C/p>\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle scoped>\n.lato {\n font-family: 'Lato';\n}\n\n.nunito {\n p {\n font-family: 'Nunito';\n }\n}\n\u003C/style>\n\n```\n\n## Reproduction steps\n\n1. Apply a font family using nuxt fonts to a nested CSS class selector.\n\n> Note that the font only applies to single-level selectors, not nested ones like `.nunito p`.\n\n## Expected behaviour\n\nBoth fonts should be applied according to the CSS structure, with `Lato` on the outer `div` and `Nunito` on the inner `\u003Cp>` element.\n\n## Reproduction link\n\n\n[Stackblitz repro](https://stackblitz.com/edit/github-5srqpg?file=app.vue)",[3111,3112],{"name":3020,"color":3021},{"name":3113,"color":3114},"good first issue","7057ff",371,"Nested CSS font-family not working as expected","2024-12-05T13:03:43Z","https://github.com/nuxt/fonts/issues/371",0.75351924,{"description":3121,"labels":3122,"number":3115,"owner":3029,"repository":3125,"state":3044,"title":3126,"updated_at":3127,"url":3128,"score":3119},"\n",[3123],{"name":3053,"color":3124},"1ad6ff","nuxt.com","Design kit classes should use new colors instead of hard-coded hex","2023-02-15T12:30:45Z","https://github.com/nuxt/nuxt.com/issues/371",{"description":3130,"labels":3131,"number":3115,"owner":3029,"repository":3043,"state":3044,"title":3132,"updated_at":3133,"url":3134,"score":3119},"Hi 👋 \r\nI am attempting to use `@nuxt/test-utils` on a fresh nuxt-project.\r\nHowever, the setup function throws with the following message: \r\n`No 'pages' directory found in \u003CPATH-TO-MY-PROJECT>/test/fixture. Did you mean to run 'nuxt' in the parent ('../') directory?`\r\n\r\nI have tried to pass `configFile` and `rootDir` with path values relative to the test file. \r\nIs this a bug or am I doing something wrong? \r\n\r\nAll help is greatly appreciated 😄 \r\n \r\nHere is the relevant code: \r\n```ts\r\n// \u003CPATH-TO-MY-PROJECT>/test/pages/index.test.ts\r\nimport { setupTest } from '@nuxt/test-utils'\r\n\r\ndescribe(\"The index page\", () => {\r\n\r\n setupTest({ server: true /*, configFile: \"../../nuxt.config.js\", rootDir: \"../../\" */});\r\n});\r\n```\r\n```ts\r\n// \u003CPATH-TO-MY-PROJECT>/jest.config.ts\r\n// jest.config.ts\r\nimport type { Config } from '@jest/types';\r\n\r\n// Sync object\r\nconst config: Config.InitialOptions = {\r\n verbose: true,\r\n preset: \"@nuxt/test-utils\",\r\n};\r\nexport default config;\r\n```",[],"Setup throws \"no 'pages' directory found\"","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/371",["Reactive",3136],{},["Set"],["ShallowReactive",3139],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEEmj2Q__dcMnJ7COUChw7G3Sz7JHxFFqonQ39CkwbFY":-1},"/nuxt/ui/2903"]