\n \u003CUSlider v-if=\"index == 'range' && typeof item == 'number'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />\n \u003CUInput v-else :type=\"index\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003Cpre class=\"w-1/2 bg-gray-200 p-4 leading-14\"> {{ state }} \u003C/pre>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst state = ref({}) // ISSUE: Default values are not loaded in the v-model\nconst items = {\n number: 50,\n reset: true, // ISSUE: UInput is not supporting boolean values for v-model\n submit: true, // ISSUE: UInput is not supporting boolean values for v-model\n search: \"search\",\n date: \"2025-04-25\",\n text: \"text\",\n color: \"#ccffcc\",\n button: true, // ISSUE: UInput is not supporting boolean values for v-model\n checkbox: false, // ISSUE: UInput is not supporting boolean values for v-model\n \"datetime-local\": \"2025-04-25T10:49:31\",\n email: \"nobody@gmail.com\",\n file: \"\",\n hidden: \"hidden\",\n image: \"image.svg\",\n month: \"2025-04\",\n password: \"topsecret\",\n radio: true, // ISSUE: UInput is not supporting boolean values for v-model\n range: 50, // Default value is displayed but not loaded in the v-model\n tel: \"0612345678\",\n time: \"10:49:31\",\n url: \"www.chatgpt.com\",\n week: \"2025-W16\"\n}\n// const state = reactive(items) // Workaround for default-value\n\u003C/script>\n```\n\n### Description\n\nI made a small comparison between `UInput` and other components like `UColorPicker` and `USlider` and I stumbled on a couple of issues.\n* `default-value` is not displayed except for `range` and `USlider`\n* `default-value` is never initialized in the `v-model`\n* Booleans are not supported in the `v-model` and I was therefore not able to make them reactive.\n\nWorkaround is to load the default value via the `state`, but that requires an additional step and is therefore not ideal for dynamic forms\n`const state = reactive(items)`\n\nWorkaround for working with booleans, but I am not sure how to apply the `v-model` yet🤔\n`\u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />`\n\n\n### Additional context\n\nDefault values via `default-value`\n\nDefault value via `state`\n\n\n### Logs\n\n```shell-script\n\n```",[3038,3039],{"name":3019,"color":3020},{"name":3022,"color":3023},3983,"closed","Default values are not loaded in the v-model","2025-06-30T13:04:54Z","https://github.com/nuxt/ui/issues/3983",0.63046116,{"description":3047,"labels":3048,"number":3051,"owner":3028,"repository":3029,"state":3041,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, css, future, compatibilityDate, vite\n- Runtime Modules: @nuxt/ui@3.1.3\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-bsi7gjhw?file=app%2Fapp.vue\n\n### Description\n\nThe UInput component behaves the same way whether using `v-model` or just `:modelValue`—it retains input values when typed into. However, this is incorrect because I did not set up the `@update:modelValue` event\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3049,3050],{"name":3019,"color":3020},{"name":3022,"color":3023},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.6397233,{"description":3057,"labels":3058,"number":3062,"owner":3028,"repository":3028,"state":3041,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.9.0`\r\n- Nuxt Version: `3.13.1`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `pnpm@9.3.0`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-yd89uq?file=app.vue,components%2FFoo.vue,components%2FBar.vue\n\n### Describe the bug\n\nI've noticed a few issues with component props after updating from Nuxt 3.12.3 to the latest version. I suspect it might be caused by enabling reactive props destructuring by default in Vue 3.5.\r\n\r\n1. setting default values for `boolean` props doesn't work (though it does for `string` props, for example)\r\n```ts\r\nconst {\r\n foo = true, // will be `false` if not provided\r\n bar = 'something', // will be `'something'` if not provided\r\n} = defineProps\u003C{\r\n foo?: boolean\r\n bar?: string\r\n}>()\r\n```\r\n2. seemingly, all prop reactivity is lost when using reactive destructure (when changing the prop values, they do not update in the component)\r\n```ts\r\n// It works correctly if defined using the \"old\" way, though\r\nconst props = defineProps\u003C{\r\n foo?: boolean\r\n bar?: string\r\n}>()\r\n```\r\n\r\n---\r\n\r\nThe behaviour was the same whether or not I had `vite.vue.script.propsDestructure` set to `true` in `nuxt.config` (though it should not be relevant now that it should be enabled by default?)\n\n### Additional context\n\nI tested it in vue SFC playground and it worked correctly there, so that's why I assume this might be a Nuxt issue\r\n\r\nhttps://play.vuejs.org/#eNqNUlFLwzAQ/ishLyqMFpm+zG6iMkEfdKiPAanttWamuZCkdTD6372kdA5x4tvd9313/fJdt/zKmKRrgc945gorjWcOfGsWQsvGoPXsBhvDKosNO0rS0AT50YXQQmfpMEJiajw0RuUeqGMsK2UXCyrjhnSA0wHP0j01n3DvCtSVrJO1Q01etkEseEGTUoF9NF6idoLPWGQClyuFn/cR87aFyYgX71B8/IKv3SZggq8sOLAdCL7jfG5r8AO9fH6ADdU7ssGyVaT+g3wCh6oNHgfZdatLsr2ni27vYqJS1y9uufGg3fioYDQo+6gXnBIOoR16+rfdaXIW54TuKcXxOj+PyVSu6znN0Zp4Kwrb+WFfhcjmY1I9lSVUUsPKonHZqLicsTdEBTnN9ovjk/8f/xaRjG/jZ3qyefgXeO3AhkDI/DQ5T055/wUEUtzf\n\n### Logs\n\n_No response_",[3059],{"name":3060,"color":3061},"pending triage","E99695",28845,"Issues with prop reactivity & default values when using reactive props destructure","2024-09-05T10:11:34Z","https://github.com/nuxt/nuxt/issues/28845",0.664835,{"description":3068,"labels":3069,"number":3073,"owner":3028,"repository":3029,"state":3041,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3070,3071,3072],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.6662667,{"description":3079,"labels":3080,"number":3085,"owner":3028,"repository":3028,"state":3041,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Environment\n\nLocal:\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v17.9.0\r\n- Nuxt Version: 3.4.0\r\n- Nitro Version: 2.3.3\r\n- Package Manager: pnpm@8.2.0\r\n- Builder: vite\r\n- User Config: runtimeConfig, modules, sanity, image, imports, typescript\r\n- Runtime Modules: @nuxtjs/sanity@1.6.0, @nuxtjs/tailwindcss@6.6.5, @nuxt/image-edge@1.0.0-28008586.381b906\r\n- Build Modules: -\r\n------------------------------\r\n\r\nStackblitz:\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.0\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[useState not working v. 3.4](https://stackblitz.com/edit/nuxt-starter-ars6vb?file=app.vue)\r\n\r\nClone to compare:\r\n[useState working v. 3.3.3](https://stackblitz.com/edit/nuxt-starter-weney3?file=app.vue)\r\n\r\n\n\n### Describe the bug\n\nuseState does not update the value on interaction.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nNo errors or logs.\n```\n",[3081,3084],{"name":3082,"color":3083},"3.x","29bc7f",{"name":3060,"color":3061},20243,"useState not working in v. 3.4","2023-04-12T21:43:09Z","https://github.com/nuxt/nuxt/issues/20243",0.6746145,{"description":3091,"labels":3092,"number":3103,"owner":3028,"repository":3028,"state":3041,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-6wub83k1\n\n### Describe the bug\n\n`error.vue` prop `error` does not contain a `data` property since Nuxt version `3.16.0` when using `npm run build` although it is passed in `createError()`.\nWorks fine with `npm run dev`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3093,3094,3097,3100],{"name":3019,"color":3020},{"name":3095,"color":3096},"nitro","bfd4f2",{"name":3098,"color":3099},"🔨 p3-minor","FBCA04",{"name":3101,"color":3102},"possible regression","B90A42",31449,"error.vue does not contain error.data property in build","2025-03-28T15:05:23Z","https://github.com/nuxt/nuxt/issues/31449",0.6749887,{"description":3109,"labels":3110,"number":3113,"owner":3028,"repository":3028,"state":3041,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.6.1\r\n- Nuxt Version: 3.9.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.8.1\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nAdd this to an existing project or create a new project...\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ca href=\"https://nuxt.com/\" :target=\"linkTarget\" ref=\"link\"> nuxt.com \u003C/a>\r\n \u003Cdl>\r\n \u003Cdt>expected\u003C/dt>\r\n \u003Cdd>{{ linkTarget }}\u003C/dd>\r\n \u003Cdt>actual\u003C/dt>\r\n \u003Cdd>{{ $refs.link?.target }}\u003C/dd>\r\n \u003C/dl>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\" setup>\r\nconst linkTarget = computed(() => (process.server ? \"server\" : \"client\"));\r\n\u003C/script>\r\n```\n\n### Describe the bug\n\nWhen the server generates a value, in this case \"server\" ... and when the client hydrates and changes the value, in this case to \"client\", the hydration doesn't update the value passed to component props. However if the value is changed to anything other than the two values then it picks up the change immediately.\n\n### Additional context\n\nIn my actual case I was using the [@vueuse/useMediaQuery](https://vueuse.org/core/useMediaQuery/) composable to set a prop based on screensize. On server it would always default to \"mobile\" because it doesn't have access to the screen size, however if you loaded it on a larger screen (like a desktop or laptop) it would get a different value. Resizing the screen would have no effect until it went into the \"mobile\" threshold, and then back out of it.\n\n### Logs\n\n_No response_",[3111,3112],{"name":3082,"color":3083},{"name":3060,"color":3061},25183,"When a prop has two possible values and the server sets one, and the client sets the other it loses initial reactivity to other props","2024-01-13T00:59:38Z","https://github.com/nuxt/nuxt/issues/25183",0.67555046,{"description":3119,"labels":3120,"number":3124,"owner":3028,"repository":3029,"state":3041,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@10.12.4\n- Builder: -\n- User Config: -\n- Runtime Modules: @nuxt/ui@3.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/serene-river-hypccq\n\n### Description\n\nupdating to 3.2.0, the cancel button does not display\n\n```ts\nconst overlay = useOverlay()\nconst dialog = overlay.create(VDialog, {\n props: {\n showCancelButton: true,\n },\n})\n\nfunction showDialog() {\n dialog.open({\n title: 'Lorem Ipsum',\n description: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',\n })\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3121,3122,3123],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4468,"useOverlay: passing props to open will override the props of the create","2025-07-08T08:51:35Z","https://github.com/nuxt/ui/issues/4468",0.67799795,{"description":3130,"labels":3131,"number":3139,"owner":3028,"repository":3029,"state":3041,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Environment\n\nOperating System: Linux\r\nNode Version: v20.15.1\r\nNuxt Version: 3.13.0\r\nCLI Version: 3.13.1\r\nNitro Version: 2.9.7\r\nPackage Manager: bun@1.1.27\r\nBuilder: -\r\nUser Config: devtools, extends, modules, ui\r\nRuntime Modules: @nuxt/ui@2.18.4\r\nBuild Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\n-\n\n### Description\n\n```\r\nType '{ \"v-model\": string | undefined; icon: string; type: string; size: \"md\"; placeholder: string; autocomplete: string; }' is not assignable to type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n Property 'autocomplete' does not exist on type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n```\n\n### Additional context\n\n`UInput` component doesn't have the default input types (`HTMLInputElement`)\n\n### Logs\n\n_No response_",[3132,3133,3134,3137],{"name":3019,"color":3020},{"name":3025,"color":3026},{"name":3135,"color":3136},"closed-by-bot","ededed",{"name":3138,"color":3136},"stale",2104,"`UInput` default types","2025-06-18T09:06:12Z","https://github.com/nuxt/ui/issues/2104",0.6785119,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftsX4s7MTtFWoJE3j57rJH6RdScDOA0tbhJRe5VCNAVI":-1},"/nuxt/ui/4569"]