\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_",[2015],{"name":1985,"color":1986},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.5717819,{"description":2022,"labels":2023,"number":2025,"owner":1988,"repository":1988,"state":2007,"title":2026,"updated_at":2027,"url":2028,"score":2029},"### 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_",[2024],{"name":1985,"color":1986},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.60484505,{"description":2031,"labels":2032,"number":2037,"owner":1988,"repository":1988,"state":2007,"title":2038,"updated_at":2039,"url":2040,"score":2041},"### 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_",[2033,2034],{"name":1985,"color":1986},{"name":2035,"color":2036},"upstream","E8A36D",28295,"propsDestructure no longer working ","2024-08-05T17:08:59Z","https://github.com/nuxt/nuxt/issues/28295",0.6545554,{"description":2043,"labels":2044,"number":2052,"owner":1988,"repository":1988,"state":2007,"title":2053,"updated_at":2054,"url":2055,"score":2056},"### 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_",[2045,2048,2051],{"name":2046,"color":2047},"documentation","5319e7",{"name":2049,"color":2050},"3.x","29bc7f",{"name":1985,"color":1986},25050,"Properties of provided values in a plugin lose template reactivity","2024-01-05T13:43:37Z","https://github.com/nuxt/nuxt/issues/25050",0.65603286,{"description":2058,"labels":2059,"number":2064,"owner":1988,"repository":1988,"state":2007,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### 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_",[2060,2061],{"name":1985,"color":1986},{"name":2062,"color":2063},"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.6625368,{"description":2070,"labels":2071,"number":2074,"owner":1988,"repository":1988,"state":2007,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Environment\r\n\r\n```\r\nNuxi 3.3.3\r\n\r\nRootDir: /project/home/benjaminrobinet/workspace\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `pnpm@7.1.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/sandbox/reactivity-issue-dlxt09\r\n\r\nThe page `index.vue` is mutating the reactive object, and the component `StateComponent.vue` is displaying the value and using it to apply a CSS class using a computed.\r\n\r\n### Describe the bug\r\n\r\nHere we have a useState method that is mutated to another value on the setup of a page. The template reacts well when using `{{ stateValue }}`, but not in computed, template binding, etc...\r\n\r\nI added a button to mutate the state on a nextTick, and it works as expected. That's probably not a useState issue, as I have the same issue with Pinia.\r\n\r\nEDIT: On HMR, it works fine.\r\n\r\nThe expected behavior is that everything should be correctly reactive to that reactive object.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2072,2073],{"name":2049,"color":2050},{"name":1985,"color":1986},20130,"Reactivity / hydratation issue on render with reactive object","2023-04-07T13:50:33Z","https://github.com/nuxt/nuxt/issues/20130",0.66447365,{"description":2080,"labels":2081,"number":2084,"owner":1988,"repository":1988,"state":2007,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.17.1`\r\n- Nuxt Version: `3.12.1`\r\n- CLI Version: `3.12.0`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `npm@9.6.7`\r\n- Builder: `-`\r\n- User Config: `runtimeConfig`, `ssr`, `telemetry`, `typescript`, `app`, `css`, `modules`, `build`\r\n- Runtime Modules: `@nuxt/eslint@0.3.13`, `@nuxtjs/tailwindcss@6.12.0`, `@vueuse/nuxt@10.11.0`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-kttbxc?file=plugins%2Ftest.ts,app.vue,components%2FChangeTestButton.vue\r\n\r\n### Describe the bug\r\n\r\nWhen ssr: false, useState is not reactive across the application when used in a plugin.\r\n\r\nIf you set ssr: true, the reactivity issue goes away.\r\n\r\nThis was not an issue in 3.11.2.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nThere are no logs.\r\n```\r\n",[2082,2083],{"name":2049,"color":2050},{"name":1985,"color":1986},27620,"useState inside plugin is not reactive when ssr: false","2024-06-15T13:55:27Z","https://github.com/nuxt/nuxt/issues/27620",0.6724166,{"description":2090,"labels":2091,"number":2094,"owner":1988,"repository":1988,"state":2007,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### 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_",[2092,2093],{"name":2049,"color":2050},{"name":1985,"color":1986},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.67265576,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"TgBh9PbtF6lkzpsn1GAH0VqfegRAgC08_wGgeEIyqcg":-1},"/nuxt/nuxt/28845"]