\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2899,2900],{"name":2885,"color":2886},{"name":2901,"color":2902},"v3","49DCB8",3299,"closed","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.72414917,{"description":2910,"labels":2911,"number":2916,"owner":2866,"repository":2891,"state":2904,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### 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_",[2912,2913],{"name":2885,"color":2886},{"name":2914,"color":2915},"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.7273385,{"description":2922,"labels":2923,"number":2926,"owner":2866,"repository":2891,"state":2904,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### 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```",[2924,2925],{"name":2885,"color":2886},{"name":2901,"color":2902},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.7304018,{"description":2932,"labels":2933,"number":2937,"owner":2866,"repository":2891,"state":2904,"title":2938,"updated_at":2939,"url":2940,"score":2941},"I am trying to create breadcrumbs that dynamically reflect route parameters in Nuxt, specifically for routes with dynamic segments. For example, when editing a user at the route `/users/:userId/edit`, the breadcrumbs should look like this: `Users > :userId > Edit`.\n\nI understand that I can use overrides with `useBreadcrumbItems()` to manually define the breadcrumb structure, but the challenge arises when different routes require different overrides. Since `useBreadcrumbItems()` can only be used at the top level of the `setup` function, I am unable to recreate or modify the breadcrumb items based on route changes. This results in errors when trying to update the breadcrumbs dynamically as the route changes.\n\nIs there a recommended way to handle this scenario where breadcrumbs need to be updated dynamically based on route parameters?",[2934],{"name":2935,"color":2936},"question","d876e3",2305,"Unable to Dynamically Generate Dynamic Breadcrumbs","2024-10-04T07:52:07Z","https://github.com/nuxt/ui/issues/2305",0.7351221,{"description":2943,"labels":2944,"number":2947,"owner":2866,"repository":2891,"state":2904,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\n\nOperating System: Windows_NT\nNode Version: v20.18.0\nNuxt Version: -\nCLI Version: 3.14.0\nNitro Version: -\nPackage Manager: unknown\nBuilder: -\nUser Config: -\nRuntime Modules: -\nBuild Modules: -\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nCannot use v3 on stackblitz so no repo.\n\n### Description\n\nThere is no code example for the `validate-on` prop. Like how do I stop blur,input and change validations?\nhttps://ui3.nuxt.dev/components/form#input-events\n\nSearched a bit on docs github repository code and I think it is something like this:\n```\n :validate-on=\"[]\" // No validation until manual trigger: 'validate' prop\n :validate-on=\"['blur']\" // Only validate on blur(or manually)\n :validate-on=\"['blur','change','input']\" // Validate on all\n```\n\nWhen you type :validate-on=\"[]\" it suggests but I didn't know if i had to put `[]`\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2945,2946],{"name":2885,"color":2886},{"name":2901,"color":2902},2371,"[Form] Input events validate-on code example missing.","2024-10-23T20:25:52Z","https://github.com/nuxt/ui/issues/2371",0.7435473,{"description":2953,"labels":2954,"number":2955,"owner":2866,"repository":2956,"state":2904,"title":2957,"updated_at":2958,"url":2959,"score":2960},"",[],1031,"nuxt.com","Move nuxtjs.org to v2.nuxt.com","2023-01-09T16:01:37Z","https://github.com/nuxt/nuxt.com/issues/1031",0.7435977,{"description":2962,"labels":2963,"number":2968,"owner":2866,"repository":2891,"state":2904,"title":2969,"updated_at":2906,"url":2970,"score":2971},"### Description\n\nThe Nuxt UI v2 dropdown has the option to open on hover or click. In v3 the only option available is click. \n\n\n\n### Additional context\n\n_No response_",[2964,2967],{"name":2965,"color":2966},"enhancement","a2eeef",{"name":2901,"color":2902},3322,"[DropdownMenu] (v3) missing mode prop for hover/click","https://github.com/nuxt/ui/issues/3322",0.74600416,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMwNREDLwRxPeWA4kgDqV3IlYXgmAtm_IBq8_NsCya4c":-1},"/nuxt/ui/3075"]