\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```",[2915,2916],{"name":2866,"color":2867},{"name":2884,"color":2885},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.71253693,{"description":2923,"labels":2924,"number":2932,"owner":2872,"repository":2887,"state":2933,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Description\n\n### Description\n\n**Problem Statement:**\nWhen using a horizontal layout, having too many menu items can lead to a cluttered interface on smaller screens. This can negatively impact the user experience as the menu becomes overwhelming or improperly formatted.\n\n\n\n**Desired Functionality:**\nWe propose that \u003CUNavigationMenu> implements an internal mechanism to manage responsive menu item display. This functionality should work as follows:\n\n**Horizontal Mode:**\nWhen the menu is rendered horizontally, items that are configured with the optional hideOnMobile property should only be displayed if the screen width exceeds the specified breakpoint (e.g., 'lg'). This allows for a cleaner, less crowded horizontal menu on mobile devices.\n\n**Fallback Behavior:**\nIf a menu item does not have a hideOnMobile property defined, it should always be displayed, regardless of screen size.\n\n**Vertical Mode:**\nThe responsive hiding functionality should only apply when the menu is in horizontal mode. In vertical mode, all menu items should remain visible, independent of any hideOnMobile settings.\n\n\n\n**Benefits for Developers:**\nThis approach provides a clear and flexible API, allowing developers to simply set the desired breakpoint directly in the menu items configuration. The \u003CUNavigationMenu> component will then automatically apply the appropriate CSS classes based on the current layout and screen size. This keeps the menu configuration clean and minimizes manual CSS adjustments while ensuring a consistent and user-friendly interface across different devices.\n\n\n\n```\nconst items = [\n {\n label: 'Always Visible',\n to: '/always'\n },\n {\n label: 'Responsive Item',\n to: '/responsive',\n hideOnMobile: 'lg'\n }\n]\n```\n\n\n\n### Additional context\n\n_No response_\n\n### Additional context\n\n_No response_",[2925,2928,2931],{"name":2926,"color":2927},"enhancement","a2eeef",{"name":2929,"color":2930},"v3","49DCB8",{"name":2884,"color":2885},3492,"closed","Responsive Menu Items in \u003CUNavigationMenu>","2025-03-28T17:42:33Z","https://github.com/nuxt/ui/issues/3492",0.574615,{"description":2939,"labels":2940,"number":2943,"owner":2872,"repository":2887,"state":2933,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### 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```",[2941,2942],{"name":2866,"color":2867},{"name":2929,"color":2930},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.66232395,{"description":2949,"labels":2950,"number":2953,"owner":2872,"repository":2887,"state":2933,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### 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_",[2951,2952],{"name":2866,"color":2867},{"name":2929,"color":2930},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.6748107,{"description":2959,"labels":2960,"number":2968,"owner":2872,"repository":2872,"state":2933,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### Discussed in https://github.com/nuxt/nuxt/discussions/19742\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **nzuyanov** March 16, 2023\u003C/sup>\r\nHi all! I need to manually split chunks in my project. Following the rollup documentation I used the `vite.build.rollupOptions.output.manualChunks` property of nuxt config.\r\nBut after running ```npm run generate```, I see a lot of errors in the console.\r\n\r\n```\r\n ERROR [nuxt] [request error] [unhandled] [500] Maximum call stack size exceeded\r\n at getModuleDependencies (file://./node_modules/vue-bundle-renderer/dist/runtime.mjs:56:24) \r\n at getModuleDependencies (file://./node_modules/vue-bundle-renderer/dist/runtime.mjs:77:21) \r\n at getModuleDependencies (file://./node_modules/vue-bundle-renderer/dist/runtime.mjs:77:21) \r\n at getModuleDependencies (file://./node_modules/vue-bundle-renderer/dist/runtime.mjs:77:21) \r\n```\r\n\r\nI decided to test the behavior on the latest version of nuxt and separate `vue` (for example) into a separate chunk, and the rest of `node_modules` into `vendors` chunk. The same error appeared in the console.\r\n\r\nMaybe I'm doing something wrong, but it could be a bug.\r\n\r\n### Environment\r\nNuxt Version: `3.3.1`\r\nNitro Version: `2.3.1`\r\nBuilder: `vite`\r\n\r\n### Reproduction\r\nhttps://stackblitz.com/edit/github-qwhmub?file=nuxt.config.ts\u003C/div>",[2961,2964,2965],{"name":2962,"color":2963},"3.x","29bc7f",{"name":2866,"color":2867},{"name":2966,"color":2967},"🔨 p3-minor","FBCA04",19837,"[nuxt] [request error] [unhandled] [500] Maximum call stack size exceeded","2023-05-28T10:55:35Z","https://github.com/nuxt/nuxt/issues/19837",0.6817148,{"description":2974,"labels":2975,"number":2979,"owner":2872,"repository":2887,"state":2933,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nThank you in advance for your help!\n\nWe’re using Nuxt UI Pro for styling in our application, which primarily uses a language other than English. When working with the `SelectMenu` component and enabling the `multiple` prop, the displayed value shows \"1 selected\" (or similar text like \"{x-number} selected\"). Instead, we’d like to display the actual selected value(s) of the SelectMenu, like when NOT using the `multiple` prop, if just one item is selected. And any more than that, we need to display the \"{x-number} selected\" it in our language, not English.\n\nDo I need to create a custom wrapper component for this, or is there a simpler way to customize the displayed text? I’m not that deep on frontend development and manipulating package classes in Nuxt 3, so I’d appreciate guidance on how to approach this issue.\n\nI’ve reviewed the source code here: https://github.com/nuxt/ui/blob/dev/src/runtime/components/forms/SelectMenu.vue but couldn’t figure out how to achieve this.\n\nI see the code where the const for the label is generated, but whats the best approach to change that for us?\n\n```\n const label = computed(() => {\n if (!props.modelValue) return null\n\n if (Array.isArray(props.modelValue) && props.modelValue.length) {\n return `${props.modelValue.length} selected`\n } else if (['string', 'number'].includes(typeof props.modelValue)) {\n return props.valueAttribute ? accessor(selected.value, props.optionAttribute) : props.modelValue\n }\n\n return accessor(props.modelValue as Record\u003Cstring, any>, props.optionAttribute)\n })\n```\n\nAny advice or direction would be greatly appreciated!",[2976],{"name":2977,"color":2978},"question","d876e3",2867,"How can I change the \u003CUSelectMenu> to display the value of a selected item, instead of \"1 selected\" when adding the multiple prop","2024-12-09T11:50:53Z","https://github.com/nuxt/ui/issues/2867",0.6827782,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fm3V80aXwWP6EBIpQF9WUL36H9mXh_hawfKNVmV_VLhk":-1},"/nuxt/ui/2609"]