\n\n### Describe the bug\n\nWhen I add \u003C Link rel=\"alternate\" >, it appears duplicated in the client-side HTML, whereas \u003C Link rel=\"canonical\" > doesn鈥檛 have this issue. Could this be a bug in unhead? Google Search Console is picking up these duplicate alternate tags.\n\n```\n\u003Ctemplate>\n \u003Cdiv>\n \u003CHtml>\n \u003CLink rel=\"alternate\" :href=\"useRoute().fullPath\" />\n\n \u003CLink rel=\"canonical\" :href=\"useRoute().fullPath\" />\n \u003C/Html>\n\n \u003CNuxtLayout>\n \u003CNuxtPage />\n \u003C/NuxtLayout>\n \u003C/div>\n\u003C/template>\n\n```\n\n### Additional context\n\nunhead@2.0.12\n\nNuxt 4 same problem\n\n### Logs\n\n```shell-script\n\n```",[3148],{"name":3149,"color":3150},"馃敤 p3-minor","FBCA04",32670,"\u003CLink rel=\"alternate\"> duplicated in the client-side HTML","2025-07-21T13:20:24Z","https://github.com/nuxt/nuxt/issues/32670",0.7415959,{"description":3157,"labels":3158,"number":3159,"owner":3138,"repository":3139,"state":3140,"title":3160,"updated_at":3161,"url":3162,"score":3163},"Hello\nIn your playground where is a possibility to set `mode: css` and image span will have `--svg` variable which could be used as value for `mask-image`\nIn `getIconCss` method there is property `mode: mask` which can return this variable\nhttps://iconify.design/docs/libraries/utils/get-icon-css.html#geticoncss\n\nIn latest `@nuxt/icon` svg content in `mode: css` always uses as `background-image` value/\n\nCan you add property which allows to get `--svg` variable which could be used as value for `mask-image`?",[],367,"Use css icon data as mask-image","2025-03-12T12:15:51Z","https://github.com/nuxt/icon/issues/367",0.74484074,{"description":3165,"labels":3166,"number":3173,"owner":3138,"repository":3174,"state":3175,"title":3176,"updated_at":3177,"url":3178,"score":3179},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nIn my Nuxt 3 project (that uses Nuxt UI `v3.0.0-alpha9`), I have a Vue component like this:\n\n```vue\n\u003Cscript setup lang=\"ts\">\n...\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUContainer class=\"section\">\n ...\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cstyle scoped lang=\"scss\">\n@use \"tailwindcss\";\n\n.section + .section {\n @apply mt-8 lg:mt-12;\n}\n\u003C/style>\n```\n\nThe problem is that `@apply mt-8 lg:mt-12;` doesn't work unless I add this to my `nuxt.config.ts`:\n```\npostcss: {\n plugins: {\n \"@tailwindcss/postcss\": {}, // https://tailwindcss.com/docs/v4-beta#using-post-css\n },\n},\n```\n\nHowever, when I do this, the Nuxt UI components stop working properly (e.g., Slideover renders at the bottom of the page and with wrong styling). How can I make the `@apply ...` work without breaking the Nuxt UI components?\n\nThis is my `package.json`:\n```json\n{\n \"name\": \"frontend\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"postinstall\": \"husky install && nuxt prepare\",\n \"dev\": \"nuxt dev\",\n \"build\": \"nuxt build\",\n \"preview\": \"nuxt preview\"\n },\n \"dependencies\": {\n \"@nuxt/ui\": \"^3.0.0-alpha.9\",\n \"nuxt\": \"latest\",\n \"nuxt-svgo\": \"latest\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"devDependencies\": {\n \"@commitlint/cli\": \"latest\",\n \"@commitlint/config-conventional\": \"latest\",\n \"husky\": \"latest\",\n \"sass\": \"latest\"\n }\n}\n```\n\nThis is my `nuxt.config.ts`:\n```ts\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: \"2024-04-03\",\n devtools: { enabled: false },\n modules: [\"@nuxt/ui\", \"nuxt-svgo\"],\n css: [\"@/assets/css/main.css\"],\n // postcss: {\n // plugins: {\n // \"@tailwindcss/postcss\": {}, // https://tailwindcss.com/docs/v4-beta#using-post-css\n // },\n // },\n appConfig: {\n // https://ui3.nuxt.dev/getting-started/theme#colors\n ui: {\n colors: {\n primary: \"primary\", // Defined in `assets/css/theme.css`\n secondary: \"secondary\", // Defined in `assets/css/theme.css`\n },\n },\n },\n});\n```\n\nThis is my `assets/main.css`:\n```css\n/* https://ui3.nuxt.dev/getting-started/installation/nuxt#import-tailwind-css-and-nuxt-ui-in-your-css */\n@import \"tailwindcss\";\n@import \"@nuxt/ui\";\n```",[3167,3170],{"name":3168,"color":3169},"question","d876e3",{"name":3171,"color":3172},"v3","49DCB8",2772,"ui","closed","@apply Tailwind CSS class in a component's `\u003Cstyle>` tag","2024-12-09T11:14:28Z","https://github.com/nuxt/ui/issues/2772",0.71090686,{"description":3181,"labels":3182,"number":3183,"owner":3138,"repository":3184,"state":3175,"title":3185,"updated_at":3186,"url":3187,"score":3188},"Each time the project is restarted or changed, the following error occurs:\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 3 retries left. 19:30:58 \n\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 2 retries left. 19:31:09 \n\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 1 retries left. 19:31:20 \n\n\n ERROR Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed \n ERROR Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed",[],424,"fonts","Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed","2025-03-17T08:56:47Z","https://github.com/nuxt/fonts/issues/424",0.72191274,{"description":3190,"labels":3191,"number":3199,"owner":3138,"repository":3174,"state":3175,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`, `css`, `colorMode`, `build`, `runtimeConfig`, `app`, `lodash`, `vite`, `router`, `nitro`\n- Runtime Modules: `@pinia/nuxt@0.9.0`, `pinia-plugin-persistedstate/nuxt@4.2.0`, `@nuxt/test-utils/module@3.17.2`, `@vueuse/nuxt@11.3.0`, `nuxt-countdown@1.2.0`, `nuxt-lodash@2.5.3`, `nuxt-monaco-editor@1.3.1`, `@nuxt/eslint@1.2.0`, `@nuxt/eslint@1.2.0`, `@nuxt/fonts@0.11.0`, `@nuxt/icon@1.11.0`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.2`, `@nuxt/test-utils@3.17.2`, `@nuxt/ui@3.0.1`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nervous-flower-vv52gy\n\n### Description\n\nActions template does not render in Alert\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3192,3195,3196],{"name":3193,"color":3194},"bug","d73a4a",{"name":3171,"color":3172},{"name":3197,"color":3198},"triage","ffffff",3950,"Alert","2025-04-21T16:25:55Z","https://github.com/nuxt/ui/issues/3950",0.7260136,{"description":3205,"labels":3206,"number":3213,"owner":3138,"repository":3214,"state":3175,"title":3215,"updated_at":3216,"url":3217,"score":3218},"With the pinia nuxt module you can set `autoImports` in the configuration. I have something like this in mine:\r\n\r\n```\r\npinia: {\r\n autoImports: [['defineStore', 'definePiniaStore']],\r\n},\r\n```\r\nThat allows me to auto import `definePiniaStore` which is a reference to `defineStore`. \r\n\r\nThe import is not found when I try to test the store using nuxt-vitest. Is there something nuxt-vitest could do to support them? Or is it something that pinia needs to fix with their module on their end?",[3207,3210],{"name":3208,"color":3209},"vitest-environment","b60205",{"name":3211,"color":3212},"needs reproduction","DE7793",592,"test-utils","Support pinia autoImports","2023-12-02T00:22:10Z","https://github.com/nuxt/test-utils/issues/592",0.7296713,{"description":3220,"labels":3221,"number":3222,"owner":3138,"repository":3223,"state":3175,"title":3224,"updated_at":3225,"url":3226,"score":3227},"# Issue\nInitial browsing to `http://localhost:3000` in **dev mode** will get error page:\n\n\n\n# Dev Environment\n- OS: **Windows 10 x64**\n- Browser: **Microsoft Edge**\n- nodejs: **v20.18.2**\n- pnpm: **9.15.4**\n\n\n\n# Repro\n1. Follow setup instructions of `README.md`\n2. Execute `pnpm dev`\n\n\n\n3. Open browser on `http://localhost:3000/` will come up with server error log and according browser view:\n\n\n\n\n\n# Fix / Analysis\n**Update by 10-Feb-2025:**\nA dependency upgrade to Nuxt 3.15.4 will resolve that issue. It looks that the root cause has been fixed by this [Nuxt PR](https://github.com/nuxt/nuxt/pull/30802).\nPR #1784 resolves this issue.",[],1783,"nuxt.com","500 error on landing page route \"/\" in dev mode caused by emojilib","2025-03-21T19:06:05Z","https://github.com/nuxt/nuxt.com/issues/1783",0.72988594,{"description":3229,"labels":3230,"number":3236,"owner":3138,"repository":3174,"state":3175,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Description\n\nBreadcrumb uses Link (and LinkBase) to implement the item rendering and navigation. Link (through LinkBase) in itself supports `onClick` event/prop. Now, passing `onClick` to the breadcrumb item does not go all the way through to the LinkBase, and thus prevents the fine-grained control of the Breadcrumb component.\n\nThe usage would look something like this:\n```\n\u003Ctemplate>\n \u003CUBreadcrumb :items=\"items\" />\n\u003C/template>\n\u003Cscript setup>\nconst items = [\n { label: \"click for one\", onClick: () => alert(\"1\"), to: \"/one\" },\n { label: \"click for two\", onClick: () => alert(\"2\"), to: \"/two\" },\n]\n\u003C/script>\n```\n\nMy need is to have some secondary effects happening besides the navigation when the user clicks on a breadcrumb item.\n\n### Additional context\n\n_No response_",[3231,3234,3235],{"name":3232,"color":3233},"enhancement","a2eeef",{"name":3171,"color":3172},{"name":3197,"color":3198},3631,"Support for `onClick` event on Breadcrumb items","2025-03-24T18:08:16Z","https://github.com/nuxt/ui/issues/3631",0.7310648,{"description":3242,"labels":3243,"number":3246,"owner":3138,"repository":3174,"state":3175,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3244,3245],{"name":3193,"color":3194},{"name":3171,"color":3172},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.7346518,["Reactive",3252],{},["Set"],["ShallowReactive",3255],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKf2uwIJqI78ZDCm-9QICPddS6DaGEP3g_ClYnHnIEjs":-1},"/nuxt/ui/2281"]