\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```",[2878,2881],{"name":2879,"color":2880},"bug","d73a4a",{"name":2882,"color":2883},"triage","ffffff",3583,"ui","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.7366694,{"description":2891,"labels":2892,"number":2899,"owner":2868,"repository":2868,"state":2870,"title":2900,"updated_at":2901,"url":2902,"score":2903},"fix: https://github.com/nuxt/nuxt/issues/14444\r\n\r\nrelated: https://github.com/nuxt/nuxt/pull/21588\r\n\r\n### Describe the feature\r\n\r\nThe docs should goes more into details/extend on the following : \r\n\r\n- how to configure vite (no vite.config, using nuxt.config, using hooks)\r\n- but also how to configure the pre-render, difference between static/generate etc\r\n- Document that `nuxi generate` is an alias of `nuxi build --prerender` (https://github.com/nuxt/nuxt/pull/21860)\r\n- link to relevant upstream docs for builder/tools etc \r\n\r\n\r\n```[tasklist]\r\n### Tasks\r\n- [ ] Add `Build` as a sub-section of deployment\r\n- [ ] Refactor Static Hosting into a general Static section, with Nitro and provider information\r\n- [ ] Replace all instances of `nuxi generate` with `nuxi build --prerender` \r\n```\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2893,2896],{"name":2894,"color":2895},"documentation","5319e7",{"name":2897,"color":2898},"discussion","538de2",21594,"[Documentation Request] More information about build, static and generate","2024-06-30T11:08:34Z","https://github.com/nuxt/nuxt/issues/21594",0.737077,{"description":2905,"labels":2906,"number":2910,"owner":2868,"repository":2869,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"Hi, i'm using nuxt-svgo to import svgs as components, and i also have nuxt-icon for icons. The issue here is that if i use nuxt-svgo to import an svg as a component, nuxt-icon adds .nuxt-icon and .nuxt-icon--fill classes, and overwrites my svg colors",[2907],{"name":2908,"color":2909},"need-repro","A50BA3",107,"closed","Nuxt-Icon keeps adding classes to non-icon svgs imported","2024-11-14T03:22:59Z","https://github.com/nuxt/icon/issues/107",0.67560804,{"description":2917,"labels":2918,"number":2925,"owner":2868,"repository":2885,"state":2911,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### For what version of Nuxt UI are you asking this question?\n\nv3-alpha\n\n### Description\n\nI'm experience problems with the VS Code Tailwind Intellisense plugin. I have used ui v2 without problems so far, but when using v3 it only shows suggestions when a tailwindcss.config.ts is freshly edited, but then after reloading or restarting VS Code, it doesn't work anymore. When it's working, it only shows a few of the classes, but not the most common ones like padding, margin etc..\n\nHas someone experienced the same issue and knows a fix for that? ",[2919,2922],{"name":2920,"color":2921},"question","d876e3",{"name":2923,"color":2924},"v3","49DCB8",2424,"V3 Intellisense not working correctly","2024-11-05T21:44:20Z","https://github.com/nuxt/ui/issues/2424",0.6979459,{"description":2931,"labels":2932,"number":2935,"owner":2868,"repository":2868,"state":2911,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the feature\n\n尊敬的Nuxt.js团队:\r\n\r\n您好!我是一名来自中国的Nuxt.js开发者。首先,我想感谢您为开源社区所做的杰出贡献。Nuxt.js是一个非常强大和易用的框架,它极大地提高了我的开发效率。\r\n\r\n然而,在使用Nuxt.js的过程中,我发现官方文档并没有中文版本。考虑到中文开发者社区的庞大规模和对Nuxt.js的广泛使用,我认为为开发文档提供中文版本将会对许多中文开发者带来极大的便利。\r\n\r\n我理解翻译文档需要时间和资源,但我相信中文开发者社区会非常乐意参与这一过程,为Nuxt.js提供高质量的中文翻译。此外,中文文档将进一步推广Nuxt.js在中文开发者中的使用,为更多的开发者带来价值。\r\n\r\n希望您能考虑这一建议,并期待Nuxt.js在未来能为更多的开发者提供更好的支持。\r\n\r\n再次感谢您的辛勤工作和对开源社区的贡献!\r\n\r\n祝好。\r\n\r\n\r\nDear Nuxt.js Team,\r\n\r\nGreetings! I am a Nuxt.js developer from China. Firstly, I would like to express my gratitude for your outstanding contributions to the open-source community. Nuxt.js is an incredibly powerful and user-friendly framework that has significantly enhanced my development efficiency.\r\n\r\nHowever, during my experience with Nuxt.js, I noticed that the official documentation does not have a Chinese version. Given the vast size of the Chinese developer community and the widespread use of Nuxt.js among them, I believe offering a Chinese version of the documentation would greatly benefit many Chinese-speaking developers.\r\n\r\nI understand that translating documentation requires time and resources. However, I am confident that the Chinese developer community would be eager to participate in this process, providing high-quality Chinese translations for Nuxt.js. Moreover, a Chinese documentation would further promote the adoption of Nuxt.js among Chinese developers, bringing value to an even broader audience.\r\n\r\nI kindly ask you to consider this suggestion, and I look forward to seeing Nuxt.js offer even better support for developers in the future.\r\n\r\nThank you once again for your hard work and dedication to the open-source community.\r\n\r\nBest regards,\r\n\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2933,2934],{"name":2894,"color":2895},{"name":2897,"color":2898},22655,"建议为Nuxt.js开发文档添加中文版本(Suggestion to Add a Chinese Version for Nuxt.js Documentation)","2024-11-17T15:32:04Z","https://github.com/nuxt/nuxt/issues/22655",0.69910014,{"description":2941,"labels":2942,"number":2945,"owner":2868,"repository":2868,"state":2911,"title":2946,"updated_at":2947,"url":2948,"score":2949},"## Motivation\r\n\r\nVue is a very international community with a lot of presence in non-english regions like China.\r\n\r\n- Many community members have proposed their help here https://github.com/nuxt/nuxt/discussions/16054\r\n- China have a (non-official ?) Chinese version of the Nuxt docs https://github.com/nuxt/nuxt/discussions/16208 : https://nuxt.com.cn/\\\r\n- A Russian translation has been discussed https://github.com/nuxt/nuxt/discussions/17351\r\n- A Ukrainian translation have been discussed https://github.com/nuxt/nuxt/issues/19926\r\n\r\nFormkit recently released an AI translation for their website docs https://formkit.com/ in 4 languages. \r\n\r\nWe could take a similar approach and combine it with the existing community translations.\r\nIn my opinion, an AI approach needs to be compatible with existing contributions, and manual modifications.\r\n\r\n## Implementation idea\r\n\r\n*Disclaimer: I'm sharing some of my thoughts about how we could build such a system, to gauge community interest in doing so. Suggestion and feedback would be very appreciated!*\r\n\r\nWe would use i18n for the docs website to handle the language strings (related docus issue https://github.com/nuxt-themes/docus/issues/770)\r\nThen to keep the translations in sync with the english source, we could run logic (maybe within the CI), that is triggered when english docs gets merged in nuxt/nuxt, and automatically open PRs for each language with a LLM translation inserted at the right location. \r\nWith such a system, the Nuxt community/team can review the LLM output and modify it before merging it for their language. \r\nAll new additions to the docs must be done in English, so that they are reflected anywhere.\r\nIf translations PRs are an issue for maintainers, we could move all of this to another repo `nuxt-international` or something.\r\n\r\nMany of the Nuxt/Unjs team members already speak 2 or more languages, so we could start out with these languages.\r\nIf this system is successful, it can be expanded and applied to other things, such as the UnJS ecosystem, or integrated with docus\r\n\r\n### Create entire translations from scratch\r\n\r\nWhile working from human written translation is more accurate, we could also experiment with entirely AI written translations. We could build a tool that translates all markdown docs content from the english source into a new language.\r\n\r\n## Bonus\r\n\r\nLook at worldwide trends for Nuxt over the last year : https://trends.google.com/trends/explore?q=nuxt,nuxtjs,nuxt.js&hl=en-GB\r\n\r\nInterestingly enough, there's more search interest for Nuxt in China than in english speaking countries.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/98146ec6-c6d7-479d-afb9-bcb7ee13bf4f\">\r\n\r\nIn fact, the anglosphere rank significantly lower than other areas.\r\n\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2943,2944],{"name":2894,"color":2895},{"name":2897,"color":2898},21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.7032078,{"description":2951,"labels":2952,"number":2954,"owner":2868,"repository":2885,"state":2911,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nIs there any way to use [Headless UI CSS modifiers](https://headlessui.com/v1/vue/disclosure#using-data-attributes) in a Nuxt app, `ui-open`, to control the set of css classes?\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { Disclosure, DisclosureButton, DisclosurePanel } from '@headlessui/vue';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CDisclosure>\n \u003CDisclosureButton>\n \u003Cdiv class=\"text-red-500 ui-open:text-cyan-700\">Button\u003C/div>\n \u003C/DisclosureButton>\n \u003CDisclosurePanel>Text\u003C/DisclosurePanel>\n \u003C/Disclosure>\n \u003C/div>\n\u003C/template>\n```",[2953],{"name":2920,"color":2921},2715,"Using Headless UI CSS modifiers inside Nuxt app","2024-11-21T17:07:05Z","https://github.com/nuxt/ui/issues/2715",0.71041936,{"description":2960,"labels":2961,"number":2967,"owner":2868,"repository":2885,"state":2911,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2962,2963,2964],{"name":2920,"color":2921},{"name":2923,"color":2924},{"name":2965,"color":2966},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.71520776,{"description":2973,"labels":2974,"number":2977,"owner":2868,"repository":2885,"state":2911,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.10.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: yarn@4.5.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.x\n\n### Reproduction\n\n```vue\n\u003Ctemplate>\n\u003CUDropdownMenu :items=\"items\">\n \u003CUAvatar\n :src=\"profilePicture\"\n size=\"lg\"\n />\n\u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst profilePicture = ref('/this/image/does/not/exist.jpg')\nconst items = [\n[{\n\tlabel: 'Logout',\n\ticon: 'i-lucide-log-out',\n}]\n]\n\u003C/script>\n```\n\n### Description\n\nWhen the `src` of the image in `UAvatar` fails to get resolved for any reason (non-existent resource, network error, refused connection from the requested host, etc), it no longer triggers the expansion of the `UDropdownMenu`. \n\nNote that this might also affect `UPopover`, but I have not tested it yet. I will be able to test it later today.\n\nP.S. @benjamincanac this was the reason I initially included it in the migration guide, because I did not know it only happens on non-resolved images\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2975,2976],{"name":2879,"color":2880},{"name":2923,"color":2924},2923,"`UAvatar` with non-resolved `src` fails to trigger `UDropdownMenu`","2025-01-25T13:12:33Z","https://github.com/nuxt/ui/issues/2923",0.7184325,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgmUttketBGmNDQVnx8qr8yxGVdKCoNHT_ybSkIt60tU":-1},"/nuxt/ui/2883"]