\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_",[3189],{"name":3138,"color":3190},"E99695",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":3197,"labels":3198,"number":3200,"owner":3141,"repository":3141,"state":3181,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### 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_",[3199],{"name":3138,"color":3190},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.60407794,{"description":3206,"labels":3207,"number":3212,"owner":3141,"repository":3141,"state":3181,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### 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_",[3208,3209],{"name":3138,"color":3190},{"name":3210,"color":3211},"upstream","E8A36D",28295,"propsDestructure no longer working ","2024-08-05T17:08:59Z","https://github.com/nuxt/nuxt/issues/28295",0.6460105,{"description":3218,"labels":3219,"number":3227,"owner":3141,"repository":3141,"state":3181,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### 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_",[3220,3223,3226],{"name":3221,"color":3222},"documentation","5319e7",{"name":3224,"color":3225},"3.x","29bc7f",{"name":3138,"color":3190},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":3233,"labels":3234,"number":3237,"owner":3141,"repository":3163,"state":3181,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Environment\n\n- Operating System: Linux\n- Node Version: v24.4.0\n- Nuxt Version: -\n- CLI Version: 3.26.4\n- Nitro Version: -\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/w6mpnq\n\n### Description\n\nThe props `defaultValue` doesn't seem to work on UInput (found this props on the documentation). The field stays empty.\n`modelValue` works \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3235,3236],{"name":3175,"color":3176},{"name":3155,"color":3156},4569,"defaultValue has no effect","2025-07-22T08:38:57Z","https://github.com/nuxt/ui/issues/4569",0.66345584,{"description":3243,"labels":3244,"number":3249,"owner":3141,"repository":3141,"state":3181,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### 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_",[3245,3246],{"name":3138,"color":3190},{"name":3247,"color":3248},"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":3255,"labels":3256,"number":3264,"owner":3141,"repository":3163,"state":3181,"title":3265,"updated_at":3266,"url":3267,"score":3268},"### 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`",[3257,3260,3261],{"name":3258,"color":3259},"question","d876e3",{"name":3155,"color":3156},{"name":3262,"color":3263},"pro","5BD3CB",3341,"License key activation error","2025-02-17T12:02:07Z","https://github.com/nuxt/ui/issues/3341",0.6736654,["Reactive",3270],{},["Set"],["ShallowReactive",3273],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTgBh9PbtF6lkzpsn1GAH0VqfegRAgC08_wGgeEIyqcg":-1},"/nuxt/nuxt/28845"]