\n \u003CIcon\n v-show=\"searching\"\n name=\"i-heroicons-arrow-path-20-solid\"\n class=\"animate-spin\"\n />\u003C/span>\n```\n\nSo, it should show `magnifying-glass` when not searching and `arrow-path` when searching. This does not work. Depending on if the view was loaded during navigation or page load it does not change or there a both. With `v-if` it works fine.\n\nHere is a reproduction with `nuxt-ui`:\nhttps://stackblitz.com/edit/nuxt-ui-7zcwsg?file=app.vue,package.json\n\nAnd here is a reproduction from `nuxt-icon-playground`:\nhttps://stackblitz.com/edit/nuxt-icon-playground-odkjmz?file=app.vue,package.json\n\nIt works with 1.7.6 but not 1.8.0 onwards. Could this be related to #300 ?\n\n---\n```\n❯ npx nuxt info\nWorking directory: /home/projects/nuxt-ui \nNuxt project info: \n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2\n- Build Modules: -\n------------------------------\n```\n",[],301,"closed","Issue with v-show on icons in 1.8.1 or 1.8.0","2024-11-20T15:03:29Z","https://github.com/nuxt/icon/issues/301",0.6729369,{"description":3165,"labels":3166,"number":3173,"owner":3140,"repository":3174,"state":3159,"title":3175,"updated_at":3176,"url":3177,"score":3178},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v23.6.1`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.21.1`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@10.0.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `future`, `devtools`, `modules`, `css`, `eslint`, `runtimeConfig`, `ui`\n- Runtime Modules: `@nuxt/ui@3.0.0-alpha.12`, `@nuxt/eslint@0.7.5`, `@nuxt/image@1.9.0`, `@vueuse/nuxt@12.5.0`, `@nuxt/content@3.0.1`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/frosty-pond-zrpyrd\n\n### Description\n\nSometimes typescript throws errors such as `Type 'string' is not assignable to type 'string[]'` when using the `ui` props on various components, despite the usage being in theory valid and working in practice.\n\nExample:\n\n```vue\n\u003CUTextarea\n :ui=\"{\n base: 'resize-none', // False positive TS error here\n }\"\n/>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3167,3170],{"name":3168,"color":3169},"bug","d73a4a",{"name":3171,"color":3172},"v3","49DCB8",3299,"ui","Wrong types in `ui` with errors Type 'string' is not assignable to type 'string[]'","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3299",0.67877305,{"description":3180,"labels":3181,"number":3184,"owner":3140,"repository":3185,"state":3159,"title":3186,"updated_at":3187,"url":3188,"score":3189},"I got a \n```\n---\ntitle: ''\n---\n```\n\nWe should not set the `title` and `description` key if empty since Content v2 will automatically takes the first `\u003Ch1>` to generate it.",[3182],{"name":3168,"color":3183},"ff281a",505,"nuxt.com","[Project] Don't generate the front-matter if values are empty","2023-02-15T12:32:27Z","https://github.com/nuxt/nuxt.com/issues/505",0.70363116,{"description":3191,"labels":3192,"number":3184,"owner":3140,"repository":3202,"state":3159,"title":3203,"updated_at":3204,"url":3205,"score":3189},"As you mentioned in the playground tests, it would be great if we can use vue-router for navigating etc. \r\nAlso really helpfull if you have dynamic routes where the API relies on some `route.params` value.",[3193,3196,3199],{"name":3194,"color":3195},"enhancement","a2eeef",{"name":3197,"color":3198},"help wanted","008672",{"name":3200,"color":3201},"vitest-environment","b60205","test-utils","(feat) Vue router support","2023-12-02T00:17:07Z","https://github.com/nuxt/test-utils/issues/505",{"description":3207,"labels":3208,"number":3213,"owner":3140,"repository":3174,"state":3159,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### 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```",[3209,3212],{"name":3210,"color":3211},"question","d876e3",{"name":3171,"color":3172},2772,"@apply Tailwind CSS class in a component's `\u003Cstyle>` tag","2024-12-09T11:14:28Z","https://github.com/nuxt/ui/issues/2772",0.7314637,{"description":3219,"labels":3220,"number":3233,"owner":3140,"repository":3140,"state":3159,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.4.2\r\n- Nitro Version: 2.4.0\r\n- Package Manager: pnpm@8.2.0\r\n- Builder: vite\r\n- User Config: app, css, modules, vite\r\n- Runtime Modules: @unocss/nuxt@0.51.8, nuxt-svgo@3.1.0\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n1. Set the `rollupOptions` with `vite.build ` in nuxt.config like below\r\n```ts\r\nrollupOptions: {\r\n output: {\r\n assetFileNames: (assetInfo) => {\r\n let extType = assetInfo.name?.split('.')[1] ?? ''\r\n if (/(png|jpe?g|svg)$/i.test(extType)) {\r\n extType ='img'\r\n } else if (/s?css$/i.test(extType)) {\r\n extType = 'css'\r\n }\r\n return `_nuxt/${extType}/[name].[hash].[ext]`\r\n }\r\n }\r\n }\r\n```\r\n2. After build, there are two dirs called css and img, but the css file use some images in img dir like that\r\n\r\n```css\r\n.some-calss {\r\n background: url('./img/a.png')\r\n}\r\n```\r\n3. So the pages cannot show the background-image because 404\r\n\n\n### Describe the bug\n\n1. The style are built like that\r\n\r\n```css\r\n.some-calss {\r\n background: url('./img/a.png')\r\n}\r\n```\r\n2. While the expected result should like that\r\n```css\r\n.some-calss {\r\n background: url('../img/a.png')\r\n}\r\n```\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3221,3224,3227,3230],{"name":3222,"color":3223},"3.x","29bc7f",{"name":3225,"color":3226},"pending triage","E99695",{"name":3228,"color":3229},"needs reproduction","FBCA04",{"name":3231,"color":3232},"closed-by-bot","ededed",20845,"Image are used in wrong reference in stylesheet file after build with rollup","2023-08-06T01:48:42Z","https://github.com/nuxt/nuxt/issues/20845",0.73279184,{"description":3239,"labels":3240,"number":3246,"owner":3140,"repository":3174,"state":3159,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### 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_",[3241,3242,3243],{"name":3194,"color":3195},{"name":3171,"color":3172},{"name":3244,"color":3245},"triage","ffffff",3631,"Support for `onClick` event on Breadcrumb items","2025-03-24T18:08:16Z","https://github.com/nuxt/ui/issues/3631",0.7382293,{"description":3252,"labels":3253,"number":3256,"owner":3140,"repository":3174,"state":3159,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### 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```",[3254,3255],{"name":3168,"color":3169},{"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.7423524,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fToKkkLjpFhGZfH9F2roRPSNJuslqbRXMxtyzVYBeYeM":-1},"/nuxt/ui/3776"]