\n \u003C/template>\n\u003C/UError>\n```\n\n### Description\n\nThe `UError` component does not render content passed through its default or named slots. Expected slot content is not appearing in the DOM.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3153,3156,3159,3162],{"name":3154,"color":3155},"bug","d73a4a",{"name":3157,"color":3158},"v3","49DCB8",{"name":3160,"color":3161},"nuxt/ui-pro","00dc82",{"name":3163,"color":3164},"triage","ffffff",4486,"ui","\u003CUError> slots not working.","2025-07-08T09:11:50Z","https://github.com/nuxt/ui/issues/4486",0.64506996,{"description":3172,"labels":3173,"number":3181,"owner":3144,"repository":3144,"state":3145,"title":3182,"updated_at":3183,"url":3184,"score":3185},"### 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",[3174,3175,3178],{"name":3138,"color":3139},{"name":3176,"color":3177},"upstream","E8A36D",{"name":3179,"color":3180},"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.65429014,{"labels":3187,"number":3192,"owner":3144,"repository":3144,"state":3145,"title":3193,"updated_at":3194,"url":3195,"score":3196},[3188,3191],{"name":3189,"color":3190},"documentation","5319e7",{"name":3138,"color":3139},13402,"Slot can't be root-element in layouts","2023-01-19T16:54:59Z","https://github.com/nuxt/nuxt/issues/13402",0.65810543,{"description":3198,"labels":3199,"number":3205,"owner":3144,"repository":3144,"state":3145,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.13.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@8.19.3\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nI know this is a requirement for bug fixes, but I'm really stacked for time on an urgent project, and wanted to log this error in case anyone else is experiencing it and has a quick answer. or if its a known bug you can provide immediate answer to. When I get a chance I'll revert and try and set one up in the coming weeks.\n\n### Describe the bug\n\nSince installing a new package, and updating node to 18 from 16, I'm suddenly seeing loads of components that are not rendering. I also see the following errors in the console.\r\n\r\n```\r\nVue received a Component that was made a reactive object. This can lead to unnecessary performance overhead and should be avoided by marking the component with `markRaw` or using `shallowRef` instead of `ref`. \r\n```\r\nand\r\n```\r\n[Vue warn]: Component is missing template or render function. \r\n```\r\n\r\nI have tried deleting nuxt and node-modules folders and re-installing. I have discovered that simply changing the component file names works, but I of course can't do this for all of them as it would require lots of code changes. But it shows this is a weird error in the way the components are compiling. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3200,3201,3202],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3203,"color":3204},"needs reproduction","FBCA04",24751,"Since updating my package.json file, many of my unchanged components are suddenly failing to render","2023-12-30T11:46:37Z","https://github.com/nuxt/nuxt/issues/24751",0.6617922,{"description":3211,"labels":3212,"number":3219,"owner":3144,"repository":3144,"state":3145,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.7.3\r\n- CLI Version: 3.8.3\r\n- Nitro Version: 2.6.3\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: modules, experimental, components\r\n- Runtime Modules: @nuxt/ui@2.8.1\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/partial-server-component-hydration-xg57p4\n\n### Describe the bug\n\nI am basing this on the following piece of documentation but I may have misunderstood what it means:\r\n\r\n> Slots can be interactive and are wrapped within a `\u003Cdiv>` with `display: contents;`\r\n- https://nuxt.com/docs/guide/directory-structure/components#server-component-context\r\n\r\nWhen a server component contains a slot and you add a non-server component to the template it is not rendered.\r\n\r\nI would expect the component to not only be rendered but also interactive.\r\n\r\nIn the same reproduction there is an example where I have tried to use `\u003CTeleport>` to achieve the same thing. This works when the server component is initially loaded but if the props of the server component change and therefore it is re-rendered the teleported component is lost.... which makes sense as the html is replaced, but seems inconsistent.\r\n\r\nIs there are way I can force the Teleport to happen again when the props have changed and the rendering has completed?\n\n### Additional context\n\nWhat I am trying to achieve is to make parts of a server component interactive by using slots.\n\n### Logs\n\n_No response_",[3213,3214,3216],{"name":3138,"color":3139},{"name":3215,"color":3204},"🔨 p3-minor",{"name":3217,"color":3218},"server components","839413",23209,"Slot within server component is never rendered and teleported content is lost on prop change.","2023-09-14T21:44:20Z","https://github.com/nuxt/nuxt/issues/23209",0.66183376,{"description":3225,"labels":3226,"number":3233,"owner":3144,"repository":3144,"state":3145,"title":3234,"updated_at":3235,"url":3236,"score":3237},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.14.12\r\n- node: 14.15.0\r\n\r\n### Reproduction\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\n\r\n1. Create Vue.js component with a named slot of your choice\r\n2. Use created component and provide the content for the slot (wrap everything in `\u003Cclient-only>` tag); example below:\r\n```\r\n\u003CStepper\r\n :steps=\"[$t('steps.one'), $t('steps.two'), $t('steps.three')]\"\r\n>\r\n \u003Ctemplate slot=\"step-1\">\r\n \u003Cdiv>\r\n \u003Cclient-only placeholder=\"Loading...\">\r\n \u003C!-- Neither a span tag nor v-calendar plugin works (tested one by one) -->\r\n \u003Cspan>Test\u003C/span>\r\n \u003Cdiv>\r\n \u003Cv-date-picker\r\n v-model=\"dates\"\r\n is-expanded\r\n trim-weeks\r\n />\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.",[3227,3229,3230],{"name":3228,"color":3164},"stale",{"name":3141,"color":3142},{"name":3231,"color":3232},"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.66352254,{"description":3239,"labels":3240,"number":3242,"owner":3144,"repository":3144,"state":3145,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\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/nuxt-starter-pjcxjvhm?file=app.vue,pages/index.vue\n\n### Describe the bug\n\n1. Open the **minimal reproduction**. \n2. Open the browser **devtools**, and you will see a Vue warning: \n\n ```text\n [Vue warn]: Component inside \u003CTransition> renders non-element root node that cannot be animated.\n ```\n\nHowever, in the provided **minimal reproduction**, the `\u003CNuxtPage>` slot contains only a single root node: \n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CNuxtPage\n :transition=\"{ name: 'fade', mode: 'out-in', appear: true }\"\n #=\"{ Component }\"\n >\n \u003Ccomponent :is=\"Component\" />\n \u003C/NuxtPage>\n \u003C/div>\n\u003C/template>\n```\n\nIf the `\u003CNuxtPage>` slot is not used, the warning does not appear, and everything works as expected. \n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3241],{"name":3141,"color":3142},30806,"`\u003CNuxtPage>` slots not working with transition","2025-02-06T18:10:38Z","https://github.com/nuxt/nuxt/issues/30806",0.6648482,{"labels":3248,"number":3252,"owner":3144,"repository":3144,"state":3145,"title":3253,"updated_at":3254,"url":3255,"score":3256},[3249,3250,3251],{"name":3138,"color":3139},{"name":3154,"color":3155},{"name":3215,"color":3204},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.6660698,{"description":3258,"labels":3259,"number":3261,"owner":3144,"repository":3144,"state":3145,"title":3262,"updated_at":3263,"url":3264,"score":3265},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v22.7.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.9.0\r\n- Builder: -\r\n- User Config: app, compatibilityDate, srcDir, devtools, modules, arco, i18n, css, postcss, pinia, imports, router, nitro, runtimeConfig, vue, vite, build\r\n- Runtime Modules: @pinia/nuxt@0.5.4, @nuxtjs/i18n@8.5.1, arco-design-nuxt-module@0.1.0\r\n- Build Modules: -\r\n\r\n\r\n### Reproduction\r\n\r\n```\r\n\u003Cscript lang=\"ts\" setup>\r\nconst layoutName = false;\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CNuxtLayout :name=\"layoutName\">\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n\u003C/template>\r\n\r\n```\r\n\r\n### Describe the bug\r\n\r\nIn Nuxt 3, when using NuxtPage as a slot within a NuxtLayout that has a dynamic name, the page does not re-render upon route changes. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3260],{"name":3141,"color":3142},28905,"NuxtPage does not re-render when used as a slot in dynamic NuxtLayout","2024-09-10T06:24:38Z","https://github.com/nuxt/nuxt/issues/28905",0.66686267,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhFp92i7jxCovYM-jfolIRGwTPZ_gztziQTg0EpVK3Qg":-1},"/nuxt/ui/4947"]