\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[2852,2855],{"name":2853,"color":2854},"enhancement","a2eeef",{"name":2856,"color":2857},"v3","49DCB8",4139,"nuxt","ui","open","USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.72500974,{"description":2867,"labels":2868,"number":2872,"owner":2859,"repository":2860,"state":2873,"title":2874,"updated_at":2875,"url":2876,"score":2877},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nDoes anyone know how to increase the width of the modal in `UModal` tag? Thanks in advance!\n\n\n",[2869],{"name":2870,"color":2871},"question","d876e3",2747,"closed","How do I increase the width of the modal in UModal tag","2024-12-05T12:47:38Z","https://github.com/nuxt/ui/issues/2747",0.7428872,{"description":2879,"labels":2880,"number":2885,"owner":2859,"repository":2860,"state":2873,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.4.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: bun@1.2.5\n- Builder: -\n- User Config: devtools, modules, imports, components, css, compatibilityDate, experimental, future\n- Runtime Modules: @nuxt/ui@3.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/recursing-browser-klwx46\n\n### Description\n\nWhen a `SelectMenu` is wrapped in a custom component which is then consumed by `FormField` validation is triggered for an instant before the component goes back to its valid state.\n\nI've tried to debug a bit and I think it's related to the fact that the `SelectMenu` uses `Input` and that input is firing a `change` event because it uses `useFormField`, even though that particular input should not be considered the \"form field\" in this instance.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/75e8c84f-612e-48f0-bf9e-dcc1fe95ffcd\n\nI'd like to open a PR and fix this myself but I'm not sure what the best approach it. Maybe `Input` could take a prop that allows it to not fire form events? i.e. `ignore-form-events=\"true\"` so the SelectMenu would use it. This could also apply for other components that use primitive form inputs inside them (Command, InputMenu) etc.\n\n### Logs\n\n```shell-script\n\n```",[2881,2884],{"name":2882,"color":2883},"bug","d73a4a",{"name":2856,"color":2857},3736,"[USelectMenu] Validation events are triggered before change when wrapped in a custom component","2025-05-14T17:24:48Z","https://github.com/nuxt/ui/issues/3736",0.74507576,{"description":2891,"labels":2892,"number":2899,"owner":2859,"repository":2859,"state":2873,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Version\r\n\r\n[v2.6.2](https://github.com/nuxt.js/releases/tag/v2.6.2)\r\n\r\n### Reproduction link\r\n\r\n[https://codesandbox.io/s/wn7j570y85](https://codesandbox.io/s/wn7j570y85)\r\n\r\n### Steps to reproduce\r\n\r\nSimply click on button named \"Mounted triggered twice, see console\" and see in console.\r\n(reproducable only with css:false for transition)\r\n\r\n### What is expected ?\r\n\r\nmounted once\r\n\r\n### What is actually happening?\r\n\r\nmounted twice\r\n\r\n### Additional comments?\r\n\r\nThe bug is still present on last release 2.7.1\r\nIt can be fixed quickly ? it's really a brake on client-side performance.\r\n(Related : https://github.com/nuxt/nuxt.js/issues/5616)\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9188\">#c9188\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2893,2896],{"name":2894,"color":2895},"pending triage","E99695",{"name":2897,"color":2898},"2.x","d4c5f9",5703,"Mounted twice when layout change","2024-08-11T06:44:28Z","https://github.com/nuxt/nuxt/issues/5703",0.74735445,{"description":2905,"labels":2906,"number":2909,"owner":2859,"repository":2860,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2907,2908],{"name":2870,"color":2871},{"name":2856,"color":2857},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.7522991,{"labels":2915,"number":2921,"owner":2859,"repository":2859,"state":2873,"title":2922,"updated_at":2923,"url":2924,"score":2925},[2916,2919,2920],{"name":2917,"color":2918},"stale","ffffff",{"name":2894,"color":2895},{"name":2897,"color":2898},6198,"Key Events blocked / not working reliably","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6198",0.7523763,{"description":2927,"labels":2928,"number":2929,"owner":2859,"repository":2930,"state":2873,"title":2931,"updated_at":2932,"url":2933,"score":2934},"Hello everyone,\r\n\r\nI have a few questions about Nuxt test-utils.\r\n\r\nMy situation:\r\n\r\n- I have a Vue.js project with Vue test-utils;\r\n- I have a Nuxt.js project where I would like to add testing;\r\n\r\nI'm looking into different options for libraries to test my Nuxt.js project. Ideally, I would like to have something very similar to Vue test-utils, in order to avoid headaches when working on both projects. Nuxt test-utils seems like an interesting option, but I was wondering what are its advantages compared to just using Vue test-utils? Thanks!",[],451,"test-utils","Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/451",0.76140594,{"description":2936,"labels":2937,"number":2942,"owner":2859,"repository":2860,"state":2873,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Environment\n\n- Operating System: Windows \n- Node Version: v20.19.0\n- Nuxt Version: 3.16.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n- install the latest version `bun add @nuxt/ui@latest`\n- remove cache and node modules `bun nuxi cleanup` `rm .\\node_modules\\`\n- then install `bun install`\n\nIn `nuxt.config.ts` add a custom prefix `{ ui: { prefix: \"Ob\" } } `\nand use the `CheckboxGroup` component as mentioned in docs (and dont forget your custom prefix).\nEx: ` \u003CObCheckboxGroup class=\"bg-red-200\" variant=\"card\" :default-value=\"['System']\" :items=\"items\" />`\n\nFinally run the code and you will see nothing will show.\n\n### Description\n\nI inspected the Dom and noticed `\u003Cucheckbox id=\"v-0-0-0-3-0-0:System\" label=\"System\" disabled=\"false\" value=\"System\">\u003C/ucheckbox>` is being used iterated for all the items. I've then inspected the node modules (\"../node_modules/@nuxt/ui/dist/runtime/components/CheckboxGroup.vue\") for that component after a clean install and saw UCheckbox is being directly used inside the CheckboxGroup component. Inside the node_module component, if i swap out UCheckbox with ObCheckbox, then the code will work as expected. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2938,2939,2940],{"name":2882,"color":2883},{"name":2856,"color":2857},{"name":2941,"color":2918},"triage",4090,"UCheckboxGroup items don't adhere to the custom prefix","2025-05-06T10:15:57Z","https://github.com/nuxt/ui/issues/4090",0.7620684,{"labels":2948,"number":2951,"owner":2859,"repository":2859,"state":2873,"title":2952,"updated_at":2953,"url":2954,"score":2955},[2949,2950],{"name":2894,"color":2895},{"name":2897,"color":2898},4132,"Page dom refreshed Before transition","2025-03-12T04:22:01Z","https://github.com/nuxt/nuxt/issues/4132",0.7630115,{"description":2957,"labels":2958,"number":2960,"owner":2859,"repository":2860,"state":2873,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Description\n\nI would like to style my Radio component like this -\n\n\nBut Nuxt UI default styling gives me this. Without much ability to customize -\n\n\nI achieved the first styling in a very hacky way. I saw the DOM of the `\u003CURadioGroup>` component and used deep selector to style child tags. Some class selectors that are used are from tailwind like the items-start (styling code in the comment section). Not the best way, but it works.\n\nIs there a more elegant and straightforward way to do this?\n",[2959],{"name":2870,"color":2871},2950,"NuxtUI custom styling of URadioGroup component","2024-12-22T15:40:17Z","https://github.com/nuxt/ui/issues/2950",0.7654928,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzabwl-xqEeZwbXz-LelCOf_ta3CP1H3mpMy-i8_JmUk":-1},"/nuxt/ui/4176"]