\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```",[2891,2894,2897],{"name":2892,"color":2893},"bug","d73a4a",{"name":2895,"color":2896},"v3","49DCB8",{"name":2898,"color":2899},"triage","ffffff",3983,"ui","Default values are not loaded in the v-model","2025-05-05T16:31:01Z","https://github.com/nuxt/ui/issues/3983",0.6897539,{"description":2907,"labels":2908,"number":2916,"owner":2871,"repository":2871,"state":2917,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\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: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-t1vjvm?file=components%2Fcomp.vue,app.vue\r\n\r\n### Describe the bug\r\n\r\nDefining props with default value using the new vue 3.5 props destructure is compiled differently in nuxt.\r\n\r\nIn the [vue playground (vue3.5.1, SSR)](https://play.vuejs.org/#__SSR__eNp9Uk1Lw0AQ/SvjXmqhpEj1UpOKSkE9aFHBy4LEZBJTN7vL7qYWQv67sxtbU1BPycx7s+/NR8sutY42DbI5i21mKu3Aomv0gsuq1so4uFa1hsKoGkbR1AeePjrf4y0YLKD7pniMSy4zJa2D2paQePx4dINCKHhRRuRHozGX8bSXIyEKHNZapA4pAoi9yiIOYpSIpwOUTZiz9HhRldHaKkm+W1/DWUbsSqB50K4icc7mEBCPpaT9eRdyzjQ42eWzd8w+fsmv7dbnOFsZtGg2yNkec6kp0fXw8uket/S/B2uVN4LY/4CPaJVovMeedtXInGwPeMHtbZhuJctnu9w6lHbXlDfqmV3gc0YT94P6q/Ufu7PoNNRx2dEUd5v0iz+YfttCoRR0xDuYPIXDAwGRyjKh90mO0H7ffWkSPNJJJJBjUUlcGaVtHCwRfjGHN6UEppKOqFscj+kzuAby9rpB4/slb7PoLDph3RcS1OLs):\r\n\r\n\r\n\r\n```js\r\n/* Analyzed bindings: {\r\n \"foo\": \"props\"\r\n} */\r\nimport { defineComponent as _defineComponent } from 'vue'\r\n\r\nconst __sfc__ = /*@__PURE__*/_defineComponent({\r\n __name: 'Comp',\r\n props: {\r\n foo: { type: Boolean, required: false, default: true }\r\n },\r\n setup(__props, { expose: __expose }) {\r\n __expose();\r\n\r\n\r\n\r\nconst __returned__ = { }\r\nObject.defineProperty(__returned__, '__isScriptSetup', { enumerable: false, value: true })\r\nreturn __returned__\r\n}\r\n\r\n});\r\nimport { ssrInterpolate as _ssrInterpolate } from \"vue/server-renderer\"\r\nfunction ssrRender(_ctx, _push, _parent, _attrs, $props, $setup, $data, $options) {\r\n _push(`${_ssrInterpolate($props.foo)}`)\r\n}\r\n__sfc__.ssrRender = ssrRender\r\n__sfc__.__file = \"src/Comp.vue\"\r\nexport default __sfc__\r\n```\r\n\r\nIn Nuxt:\r\n\r\n\r\n```js\r\nimport { createHotContext as __vite__createHotContext } from \"/_nuxt/@vite/client\";import.meta.hot = __vite__createHotContext(\"/components/comp.vue\");import { defineComponent as _defineComponent } from \"/_nuxt/node_modules/vue/dist/vue.runtime.esm-bundler.js?v=8fea97c8\";\r\nconst _sfc_main = /* @__PURE__ */ _defineComponent({\r\n __name: \"comp\",\r\n props: {\r\n foo: { type: Boolean, required: false }\r\n },\r\n setup(__props, { expose: __expose }) {\r\n __expose();\r\n const { foo = true } = __props;\r\n const __returned__ = { foo };\r\n Object.defineProperty(__returned__, \"__isScriptSetup\", { enumerable: false, value: true });\r\n return __returned__;\r\n }\r\n});\r\nimport { toDisplayString as _toDisplayString } from \"/_nuxt/node_modules/vue/dist/vue.runtime.esm-bundler.js?v=8fea97c8\";\r\nfunction _sfc_render(_ctx, _cache, $props, $setup, $data, $options) {\r\n return _toDisplayString($setup.foo);\r\n}\r\n_sfc_main.__hmrId = \"ea5b442f\";\r\ntypeof __VUE_HMR_RUNTIME__ !== \"undefined\" && __VUE_HMR_RUNTIME__.createRecord(_sfc_main.__hmrId, _sfc_main);\r\nimport.meta.hot.accept((mod) => {\r\n if (!mod) return;\r\n const { default: updated, _rerender_only } = mod;\r\n if (_rerender_only) {\r\n __VUE_HMR_RUNTIME__.rerender(updated.__hmrId, updated.render);\r\n } else {\r\n __VUE_HMR_RUNTIME__.reload(updated.__hmrId, updated);\r\n }\r\n});\r\nimport _export_sfc from \"/_nuxt/@id/__x00__plugin-vue:export-helper\";\r\nexport default /* @__PURE__ */ _export_sfc(_sfc_main, [[\"render\", _sfc_render], [\"__file\", \"/home/projects/github-t1vjvm/components/comp.vue\"]]);\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2909,2912,2913],{"name":2910,"color":2911},"workaround available","11376d",{"name":2892,"color":2893},{"name":2914,"color":2915},"🍰 p2-nice-to-have","0E8A16",28829,"closed","reactive props destructure with default values doesn't work","2024-09-24T15:17:28Z","https://github.com/nuxt/nuxt/issues/28829",0.5671796,{"description":2923,"labels":2924,"number":2926,"owner":2871,"repository":2871,"state":2917,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.18.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: yarn@1.22.22\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n\r\n### Reproduction\r\n\r\nReproduction link:\r\n\r\nhttps://stackblitz.com/edit/github-c5jyyo\r\n\r\n### Describe the bug\r\n\r\nReactive Props Destructure not working with booleans in Nuxt.\r\n\r\nCreate a simple component with:\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cp>My component with boolean value: {{ boolValue }}\u003C/p>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst {\r\n boolValue = true,\r\n} = defineProps\u003C{\r\n boolValue?: boolean;\r\n}>();\r\n\u003C/script>\r\n```\r\n\r\nUse the component:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"my-page\">\r\n \u003CSimpleComponent />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nThe expected result:\r\n\r\n`My component with boolean value: true`\r\n\r\nThe component is not inferring the default value of the prop.\r\n\r\n`My component with boolean value: false`\r\n\r\n\r\n### Additional context\r\n\r\nIn Vue 3.5.1 is working:\r\nhttps://play.vuejs.org/#eNp9UlFPwjAQ/iu1L9OEjBD0BceMGhI1UYkafVli5jjGsGubtgPMsv/uXYEJEX1q777r1+/uu5pfah0uKuADHjkotUgdxIlkLJr14rpmpc1Z00RdjHz2WpU6jrr+SGTU3XmDoc1MoR2z4CqCi1Ir41jNDExZw6ZGlSzAz4IWIp5NPuxmGCgJ0lnPT7KCc+LNlLTOSxkS1XFwA0Io9qaMmBwFJ6Rj/XPMO9xZLJ8WeTi3SmJbNelOOJEXAsyjdgXSJXzAPEJYimzLO59zpoLONp/NIPs8kJ/bFeUSPjZgwSwg4S3mUpODW8Oj5wdY4b0FSzWpBFb/Az6BVaIijeuyq0pOUPZOnVd76+dXyPzFjlYOpN02RUKpsvH1Ccch0jD/av1Hbj889e8S2eAUD3hBK7JrMBOpzIdIgYxo9tokT/yhlHhNRQXo12ZwDV4nMC0kjI3SNtqvuxj4O6QS/W7i4xM8Wk/9Zu3vpo7vv1grkS0LN9sSsAURYof1jgza4F/7il2+L8DQ5LC1fngW9njzDQjGCQ8= \r\n\r\n### Logs\r\n\r\n_No response_",[2925],{"name":2868,"color":2882},28849,"Reactive Props Destructure from Vue 3.5.1 does not work with booleans","2024-09-05T13:11:20Z","https://github.com/nuxt/nuxt/issues/28849",0.5755818,{"description":2932,"labels":2933,"number":2935,"owner":2871,"repository":2871,"state":2917,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Environment\r\n\r\n```bash\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.17.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.9.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nChanged `showThemeName` from the parent and its not reactive in the child prop.\r\n```js\r\n\u003Cscript setup lang=\"ts\">\r\nconst { showThemeName = false } = defineProps\u003C{\r\n /**\r\n * Whether to show the theme name.\r\n * @default false\r\n */\r\n showThemeName?: boolean\r\n}>()\r\n\u003C/script>\r\n```\r\n\r\n### Describe the bug\r\n\r\nI defined `showThemeName` as a prop following the Reactive Props Destructure\r\napproach supported in Vue 3.5, but still no reactivity. \r\n\r\n```js\r\n\u003Cscript setup lang=\"ts\">\r\nconst { showThemeName = false } = defineProps\u003C{\r\n /**\r\n * Whether to show the theme name.\r\n * @default false\r\n */\r\n showThemeName?: boolean\r\n}>()\r\n\u003C/script>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2934],{"name":2868,"color":2882},28885,"Reactive Props Destructure supported in Vue 3.5 still not reactive in Nuxt 3.13.1 ","2024-09-08T18:56:26Z","https://github.com/nuxt/nuxt/issues/28885",0.604078,{"description":2941,"labels":2942,"number":2947,"owner":2871,"repository":2871,"state":2917,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, vue\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-g3udp4?file=nuxt.config.ts\n\n### Describe the bug\n\nSince [@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue/blob/main/packages/plugin-vue)@5.1.0 the `propsDestructure` option should be set inside a `features` flag (see [changelog](https://github.com/vitejs/vite-plugin-vue/blob/plugin-vue@5.1.0/packages/plugin-vue/CHANGELOG.md#510-2024-07-23)) and therefore doesn't work anymore in Nuxt by setting `vue.propsDestructure: true`. I'll make a PR.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2943,2944],{"name":2868,"color":2882},{"name":2945,"color":2946},"upstream","E8A36D",28295,"propsDestructure no longer working ","2024-08-05T17:08:59Z","https://github.com/nuxt/nuxt/issues/28295",0.6460105,{"description":2953,"labels":2954,"number":2962,"owner":2871,"repository":2871,"state":2917,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.7.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.1.0\r\n- Builder: -\r\n- User Config: devServer, app, components, css, devtools, modules, auth, nitro, runtimeConfig, srcDir, vite\r\n- Runtime Modules: @nuxtjs/partytown@1.4.0, @nuxtjs/i18n@8.0.0, nuxt-jsonld@2.0.8, @nuxtjs/device@3.1.1, @nuxtjs/robots@3.0.0, nuxt-lazy-hydrate@1.0.0, @vueuse/nuxt@10.7.1, @sidebase/nuxt-auth@0.6.3\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-d8kxbk?file=app.vue,plugins%2Ftest.js\n\n### Describe the bug\n\nWhen providing objects through a plugin with reactive properties, the properties lose their reactivity when used in template directives.\r\n\r\nFor example:\r\n```html\r\n\u003Cpre>{{ $foo.bar }}\u003C/pre> \u003C!-- this is reactive -->\r\n\u003Cpre v-if=\"$foo.bar\">I should disappear\u003C/pre> \u003C!-- this is NOT reactive -->\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2955,2958,2961],{"name":2956,"color":2957},"documentation","5319e7",{"name":2959,"color":2960},"3.x","29bc7f",{"name":2868,"color":2882},25050,"Properties of provided values in a plugin lose template reactivity","2024-01-05T13:43:37Z","https://github.com/nuxt/nuxt/issues/25050",0.6632061,{"description":2968,"labels":2969,"number":2974,"owner":2871,"repository":2871,"state":2917,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\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: npm@10.2.3\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-z6juqt?file=components%2FTest.vue\r\n\r\n`npm run typecheck` in terminal\r\n\r\n```\r\ncomponents/Test.vue:8:17 - error TS2339: Property 'optionalStr' does not exist on type 'CreateComponentPublicInstanceWithMixins\u003CToResolvedProps\u003C{}, {}>, {}, {}, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, {}, VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly\u003C...> & Readonly\u003C...>, ... 16 more ..., {}>'.\r\n\r\n8 \u003Cspan v-if=\"optionalStr\">{{ optionalStr }}\u003C/span>\r\n ~~~~~~~~~~~\r\n```\n\n### Describe the bug\n\nAfter upgrading from Nuxt 3.12.3 to 3.13.2, these TS errors showed up in every component that only uses optional props. The error disappears if we add a single required prop or enable TS strict mode.\n\n### Additional context\n\nThe issue doesn't seem to be present in a pure Vue/Vite project:\r\n\r\nhttps://stackblitz.com/edit/vitejs-vite-ece16d?file=src%2Fcomponents%2FHelloWorld.vue\n\n### Logs\n\n_No response_",[2970,2971],{"name":2868,"color":2882},{"name":2972,"color":2973},"possible regression","B90A42",29041,"Components with only optional props lose props type if strict mode is disabled","2024-09-23T10:12:23Z","https://github.com/nuxt/nuxt/issues/29041",0.6639519,{"description":2980,"labels":2981,"number":2989,"owner":2871,"repository":2901,"state":2917,"title":2990,"updated_at":2991,"url":2992,"score":2993},"### Description\n\nThanks to the team for the wonderful UI library. I purchased a license for nuxt/ui-pro, but encountered an activation problem - after paying and receiving the key, I could not [activate](https://ui3.nuxt.dev/pro/activate) it, the system gave an error. `[POST] \"https://api.nuxtlabs.com/ui-pro/activate\": \u003Cno response> Failed to fetch`",[2982,2985,2986],{"name":2983,"color":2984},"question","d876e3",{"name":2895,"color":2896},{"name":2987,"color":2988},"pro","5BD3CB",3341,"License key activation error","2025-02-17T12:02:07Z","https://github.com/nuxt/ui/issues/3341",0.6736654,["Reactive",2995],{},["Set"],["ShallowReactive",2998],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTgBh9PbtF6lkzpsn1GAH0VqfegRAgC08_wGgeEIyqcg":-1},"/nuxt/nuxt/28845"]