\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2887,2890],{"name":2888,"color":2889},"bug","d73a4a",{"name":2874,"color":2875},3583,"Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.71402085,{"description":2897,"labels":2898,"number":2902,"owner":2877,"repository":2877,"state":2879,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Reproduction\n\nPut a index.html into public \n\n### Describe the bug\n\nPublic files will override routes which is fine, but it should at least warn if the route exist\n",[2899],{"name":2900,"color":2901},"pending triage","E99695",31103,"index.html in public","2025-03-11T18:04:33Z","https://github.com/nuxt/nuxt/issues/31103",0.71527064,{"description":2908,"labels":2909,"number":2911,"owner":2877,"repository":2877,"state":2879,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.3\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.0\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.4.0\n- Builder: -\n- User Config: hooks, app, experimental, ssr\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/87xie/alexander-lichter-nuxt-spa\n\nSteps to reproduce:\n1. Run `nuxt generate`\n1. Check the `.output/public` directory\n\n### Describe the bug\n\nI followed the [client-rendering documentation](https://nuxt.com/docs/guide/concepts/rendering#deploying-a-static-client-rendered-app) to create a pure client-side rendering app. However, when setting `componentIslands: true` in `nuxt.config.ts` and running `nuxt generate`, the output is missing `index.html`.\n\nCurrently, I do not explicitly enable `componentIslands`, but since I am using the [nuxt-echarts](https://github.com/kingyue737/nuxt-echarts/blob/090346ee2848f3fb3bb9019368b6f4171b1bb3db/src/module.ts#L28-L30) module, this setting is implicitly enabled.\n\nI searched for issues and discussions but found none. If I missed something, feel free to close this.\n\n### Additional context\n\nI tested different Nuxt versions and observed the following behavior:\n\n- **v3.11.2**: `index.html` exists\n- **v3.13.2**: `index.html` missing\n- **v3.16.0**: `index.html` missing\n\n### Logs\n\n```shell-script\n\n```",[2910],{"name":2900,"color":2901},31434,"Missing `index.html` when `componentIslands: true` in static client-side rendering","2025-03-19T20:16:24Z","https://github.com/nuxt/nuxt/issues/31434",0.7188837,{"description":2917,"labels":2918,"number":2919,"owner":2877,"repository":2920,"state":2879,"title":2921,"updated_at":2922,"url":2923,"score":2924},"It would be nice if you could alias and entire collection instead of just an icon.\n\nRight now I do it this way.\n```ts\nconst createIconAliases = (newPrefix: string, iconifyJson: IconifyJSON) => {\n const exisitngPrefix = iconifyJson.prefix;\n const icons = Object.keys(iconifyJson.icons);\n\n return icons.reduce(\n (object, value) => {\n object[`${newPrefix}:${value}`] = `${exisitngPrefix}:${value}`;\n return object;\n },\n {} as Record\u003Cstring, string>,\n );\n};\n```",[],362,"icon","[feature request] Allow aliasing entire collection","2025-02-21T20:10:51Z","https://github.com/nuxt/icon/issues/362",0.72282267,{"description":2926,"labels":2927,"number":2930,"owner":2877,"repository":2878,"state":2931,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Environment\n\n\n\nI get this error anytime I try and use \u003CUInput /> even without any other code.\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n`\u003Ctemplate>\n \u003CUContainer>\n \u003CUForm :schema=\"schema\" :state=\"state\" class=\"space-y-4\" @submit=\"onSubmit\">\n \u003CUFormField label=\"Code\" name=\"Code\"\n >\u003CUInput v-model=\"state.code\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { z } from 'zod';\nimport type { FormSubmitEvent } from '#ui/types';\n\nconst supabase = useSupabaseClient();\nconst toast = useToast();\n\n//Form\nconst schema = z.object({\n code: z.string().min(3),\n});\n\ntype Schema = z.output\u003Ctypeof schema>;\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n code: undefined,\n});\n\nasync function onSubmit(event: FormSubmitEvent\u003CSchema>) {\n toast.add({\n title: 'Success',\n description: 'The form has been submitted.',\n color: 'success',\n });\n console.log(event.data);\n}\n\u003C/script>\n`\n\n### Description\n\nUInput causes an error\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2928,2929],{"name":2888,"color":2889},{"name":2871,"color":2872},2349,"closed","UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.7011713,{"description":2937,"labels":2938,"number":2941,"owner":2877,"repository":2878,"state":2931,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Environment\n\n- Operating System: `macos`\n- Node Version: `v18.16.0`\n- Nuxt Version: `3.16.0\"`\n- Vue: \"3.5.0\",\n- Nuxt/ui\": \"3.0.0\",\n- CLI Version: `3.8.4`\n- Package Manager: `pnpm`\n- IDE: VS Code\n\n\n### Version\n\nv3\n\n### Reproduction\n\nin any expample, even in your ui template npx nuxi init -t ui \u003Cmy-app>\n\n\n\n### Description\n\ntailwind IntelliSense works only in attribute class of elements, but not works in :ui={...}. so to write classes in ui i need learn them all, for example. \n\n\n\n\n\n\n\n\ni tried to help tailwind IntelliSense by addnig classregex to vscode setttings, but it did not help\n\n\n\njust for test purpose, i add some classregex for [CVA](https://cva.style/docs/getting-started/installation) for check if it will work. and it work for cva, not for :ui={..}\nscreen for cva\n\n\n### Additional context\n\nmake it work please! for :ui={..} and for app.config.ts\n\n### Logs\n\n```shell-script\n\n```",[2939,2940],{"name":2888,"color":2889},{"name":2874,"color":2875},3570,"Tailwind CSS IntelliSense not works in :ui={} and in app.config.ts","2025-03-17T17:00:40Z","https://github.com/nuxt/ui/issues/3570",0.704498,{"labels":2947,"number":2952,"owner":2877,"repository":2877,"state":2931,"title":2953,"updated_at":2954,"url":2955,"score":2956},[2948,2949],{"name":2900,"color":2901},{"name":2950,"color":2951},"2.x","d4c5f9",9828,"some pages in docs not showing","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9828",0.706186,{"description":2958,"labels":2959,"number":2964,"owner":2877,"repository":2878,"state":2931,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nHello, we are currently a small team using nuxt UI pro version 2. We've seen that the new Nuxt UI 3 version is in alpha and we'd like to know if a stable release is planned soon?\n\nWe've seen that Nuxt UI 3 is going to take a long time to migrate and we'd like to start work quickly. Do you think it's cost-effective to make the switch now, or is it better to wait for a more stable version?\n\nThanks for reading ^^",[2960,2963],{"name":2961,"color":2962},"question","d876e3",{"name":2871,"color":2872},3371,"Nuxt UI V3 official release date","2025-02-21T09:22:07Z","https://github.com/nuxt/ui/issues/3371",0.70705307,{"description":2970,"labels":2971,"number":2976,"owner":2877,"repository":2878,"state":2931,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.18.3`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.22.2`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.15.4`\n- Builder: `-`\n- User Config: `extends`, `modules`, `$development`, `devtools`, `colorMode`, `runtimeConfig`, `routeRules`, `future`, `compatibilityDate`, `vite`, `typescript`, `hooks`, `echo`, `eslint`, `i18n`, `sanctum`\n- Runtime Modules: `@nuxt/content@2.13.4`, `@nuxt/eslint@0.7.6`, `@nuxt/fonts@0.10.3`, `@nuxt/image@1.9.0`, `@nuxt/ui@2.21.0`, `@nuxthq/studio@2.2.1`, `@vueuse/nuxt@12.7.0`, `nuxt-og-image@4.1.4`, `@nuxtjs/i18n@9.2.1`, `nuxt-auth-sanctum@0.5.6`, `nuxt-laravel-echo@0.2.1`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n\n### Version\n\n2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-i7bgngfx?file=app.vue\n\n### Description\n\nIf I place a USelectMenu inside a UModal that is being opened inside USlideover, I cannot focus the select menu's input.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2972,2973],{"name":2888,"color":2889},{"name":2974,"color":2975},"upstream","78bddb",3408,"USelectMenu inside UModal inside USlideover","2025-03-24T14:19:31Z","https://github.com/nuxt/ui/issues/3408",0.71528006,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7DUCFSCPmCP2ItGf_PT2UnlWj_AuZk7OS9Ahw-Vg6Tw":-1},"/nuxt/ui/2426"]