\r\n \u003C/div>\r\n \u003C/client-only>\r\n \u003C/div>\r\n \u003C/template>\r\n\u003C/Stepper>\r\n```\r\nThe placeholder remains with no content replaced as shown below:\r\n\r\n\r\n### What is Expected?\r\nContent inside `\u003Cclient-only>` tag should get rendered instead of getting stuck on the placeholder (or blank state if placeholder not provided).\r\n\r\n### What is actually happening?\r\n`\u003Cclient-only>` tag does not render its content when the tag is placed inside a component slot, as shown in the provided example. It does render when placed outside of the slot.",[3078,3081,3082],{"name":3079,"color":3080},"stale","ffffff",{"name":3067,"color":3068},{"name":3083,"color":3084},"2.x","d4c5f9",8579,"Client-only content doesn't render in component's slot","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8579",0.6703439,{"description":3091,"labels":3092,"number":3096,"owner":3029,"repository":3029,"state":3070,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Environment\n\nnuxt rc 13\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-g7nvjf?file=app.vue\n\n### Describe the bug\n\nHi :wave: this is a very small issue, currently it seems that `ClientOnly` is trying to make its default slot inherit its attributes. It triggers a warn message in the console since the default slot is rendered using a Fragment.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3093,3094,3095],{"name":3064,"color":3065},{"name":3023,"color":3024},{"name":3026,"color":3027},15444,"ClientOnly attrs are passed to the default slot","2023-01-19T17:50:34Z","https://github.com/nuxt/nuxt/issues/15444",0.67333806,{"description":3102,"labels":3103,"number":3108,"owner":3029,"repository":3029,"state":3070,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.10\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\n* Nuxt 3.5 (works): https://stackblitz.com/edit/nuxt-starter-hmzeh2mx\n* Nuxt 3.17 (broken): https://stackblitz.com/edit/nuxt-starter-ykqk1xwa\n\nThe two above reproductions only differ in `package.json` / `pnpm-lock.yaml`.\n\n### Describe the bug\n\nA page that uses legacy `asyncData` option breaks if it's used under `\u003Cclient-only>` in a parent page component.\n\nExample page (`pages/app/index.vue`):\n\n```vue\n\u003Cscript>\nexport default defineNuxtComponent({\n asyncData() {\n return {\n users: ['alice', 'bob'],\n };\n },\n});\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>Total users: {{ users.length }}\u003C/div>\n\u003C/template>\n```\n\nParent (`pages/app.vue`):\n\n```vue\n\u003Ctemplate>\n \u003Cclient-only>\n \u003Cnuxt-page />\n \u003C/client-only>\n\u003C/template>\n```\n\n`users` is undefined during the initial render, and the component crashes with \"Cannot read properties of undefined\".\n\n### Additional context\n\nThis is a regression introduced in Nuxt 3.6.\n\nIn Nuxt 3.4 and 3.5 the page works but not always. For example, what helps is having a layout with an async component (included in reproduction). In Nuxt 3.6 and later the presence of an async component in the layout doesn't help.\n\n### Logs\n\n```shell-script\n\n```",[3104,3105],{"name":3026,"color":3027},{"name":3106,"color":3107},"possible regression","B90A42",31925,"Legacy asyncData not working inside client-only page","2025-05-01T12:11:38Z","https://github.com/nuxt/nuxt/issues/31925",0.67578334,{"labels":3114,"number":3118,"owner":3029,"repository":3029,"state":3070,"title":3119,"updated_at":3120,"url":3121,"score":3122},[3115,3116,3117],{"name":3064,"color":3065},{"name":3023,"color":3024},{"name":3026,"color":3027},14563,"Usage of slots in client-only components throwing errors in production","2023-01-19T17:37:13Z","https://github.com/nuxt/nuxt/issues/14563",0.67767894,{"description":3124,"labels":3125,"number":3133,"owner":3029,"repository":3029,"state":3070,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Environment\n\nNuxi 3.0.0-rc.10 \r\nRootDir: /sandbox\r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v14.19.3`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://codesandbox.io/s/dawn-morning-b454k7?file=/pages/index.vue\r\n\r\nJuicy bit:\r\n`\u003CFooComponent>\r\n \u003Ctemplate v-if=\"true\" #first> Hello conditional \u003C/template>\r\n\u003C/FooComponent>`\n\n### Describe the bug\n\n- When rendering a component slot with a condition that evaluates to true, an error will be thrown, the slot is however rendered correctly.\r\n- It only seems to happen during SSR.\r\n- Conditions that evaluates to false does not throw an error\n\n### Additional context\n\nIn RC 8 this was working fine\n\n### Logs\n\n```shell\n[nitro] [dev] [unhandledRejection] TypeError: Cannot set property 'key' of undefined\r\n at slots.\u003Ccomputed> (/sandbox/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:2924:29)\r\n at ssrRenderSlotInner (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:628:21)\r\n at Module.ssrRenderSlot (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:618:5)\r\n at _sfc_ssrRender (/sandbox/components/FooComponent.vue:7:25)\r\n at renderComponentSubTree (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:254:17)\r\n at renderComponentVNode (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:188:16)\r\n at Module.ssrRenderComponent (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:612:12)\r\n at _sfc_ssrRender (/sandbox/pages/index.vue:60:31)\r\n at renderComponentSubTree (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:254:17)\r\n at renderComponentVNode (/sandbox/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:188:16)\n```\n",[3126,3127,3130],{"name":3064,"color":3065},{"name":3128,"color":3129},"upstream","E8A36D",{"name":3131,"color":3132},"upstream-bug","B60205",14950,"Server-side rendering a component with conditional slot causes error","2024-06-17T15:31:28Z","https://github.com/nuxt/nuxt/issues/14950",0.67988247,{"description":3139,"labels":3140,"number":3147,"owner":3029,"repository":3029,"state":3070,"title":3148,"updated_at":3149,"url":3150,"score":3151},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\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.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25196\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CClientOnly>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n \u003C/ClientOnly>\r\n\u003C/template>\r\n```\r\n\r\n### Describe the bug\r\n\r\nWhen using a `\u003CClientOnly>` component around the `App.vue` (only SSR the app shell), the NuxtLayout warning will appear even though the component is used.\r\n\r\n### Additional context\r\n\r\nRelated: https://github.com/nuxt/nuxt/issues/24912\r\n\r\n### Logs\r\n\r\n_No response_",[3141,3142,3145,3146],{"name":3064,"color":3065},{"name":3143,"color":3144},"dx","C39D69",{"name":3023,"color":3024},{"name":3053,"color":3054},25196,"`\u003CNuxtLayout /> component has not been used.` Warning when using `\u003CClientOnly>` in `app.vue`","2024-02-09T20:33:36Z","https://github.com/nuxt/nuxt/issues/25196",0.68185157,["Reactive",3153],{},["Set"],["ShallowReactive",3156],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRZEa-PqBPKnyW1s-aAagmcGMtKsWiwVXxzHFJ22KcB0":-1},"/nuxt/nuxt/27752"]