\r\n \u003C/component>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\n'use strict';\r\n\r\nexport default {\r\n props: {\r\n element: {\r\n type: String,\r\n required: false,\r\n default: 'button'\r\n }\r\n }\r\n};\r\n\u003C/script>\r\n```\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CBaseComponent>\r\n \u003Ctemplate v-for=\"(_, name) in $slots\" v-slot:[name]=\"scope\">\r\n \u003Cslot :name=\"name\" v-bind=\"scope\" />\r\n \u003C/template>\r\n \u003C/BaseComponent>\r\n\u003C/template>\r\n\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_",[2003,2004,2007],{"name":1985,"color":1986},{"name":2005,"color":2006},"pending triage","E99695",{"name":1988,"color":1989},21915,"Hydration error for slot \"inheritance\" on dynamic components","2023-07-25T06:43:06Z","https://github.com/nuxt/nuxt/issues/21915",0.6628747,{"labels":2014,"number":2022,"owner":1994,"repository":1994,"state":1995,"title":2023,"updated_at":2024,"url":2025,"score":2026},[2015,2018,2019],{"name":2016,"color":2017},"stale","ffffff",{"name":2005,"color":2006},{"name":2020,"color":2021},"2.x","d4c5f9",5613,"Cannot render nested dynamic components","2023-01-22T15:33:04Z","https://github.com/nuxt/nuxt/issues/5613",0.6743353,{"labels":2028,"number":2029,"owner":1994,"repository":1994,"state":1995,"title":2030,"updated_at":2031,"url":2032,"score":2033},[],13198,"Production build + custom vue lib + ssr","2023-01-19T16:48:28Z","https://github.com/nuxt/nuxt/issues/13198",0.6800677,{"description":2035,"labels":2036,"number":2038,"owner":1994,"repository":1994,"state":1995,"title":2039,"updated_at":2040,"url":2041,"score":2042},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.9.0\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: devtools, components\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-3-bug-vl98j5\n\n### Describe the bug\n\nThe problem only occurs with the production build.\r\nIf a component is imported dynamically and uses components common to its sub-components (e.g. a composable) and this sub-component is used elsewhere in the code, then SSR rendering of the component no longer occurs.\r\nIn my example in dev mode, the final rendering of the page is :\r\n```\r\nHello\r\nTest : foo\r\nTest Child : foo\r\nTest Child 2\r\nTest Child 2 Child : foo\r\nTest Child 2\r\nTest Child 2 Child : foo\r\n```\r\nUnfortunately, in prod mode, the ssr rendering is as follows : \r\n```\r\nHello\r\nTest : foo\r\nTest Child : foo\r\nTest Child 2\r\nTest Child 2 Child : foo\r\n```\r\nAs the client-side setup also executes for hydration, the rendering updates correctly and everything is displayed, but there is a problem with the SSR rendering.\r\nThere are no errors during the nuxt build or when generating the page on the SSR side.\r\nI think the problem must come from rollup because if you look in the file `.output/server/chunks/BaseTestChild2-WlFZNhyr.mjs` there is an export of several elements.\r\n```\r\nconst BaseTestChild2 = /* @__PURE__ */ Object.freeze({\r\n __proto__: null,\r\n default: _sfc_main\r\n});\r\n\r\nexport { BaseTestChild2 as B, _sfc_main as _, useFoo as u };\r\n```\r\nIf we compare it to a normal component (`.output/server/chunks/BaseTest-DrvCz1q7.mjs`), the export is different.\r\n```\r\nexport { _sfc_main as default };\r\n```\r\nFor me, the problem comes from the fact that it creates an object with `default: _sfc_main` before exporting it.\r\nWhen we look at the use of these files in `.output/server/server.mjs` there is a difference.\r\n```\r\nsetup(__props) {\r\n const BaseTest = defineAsyncComponent(\r\n () => import('./BaseTest-DrvCz1q7.mjs')\r\n );\r\n const BaseTestChild2 = defineAsyncComponent(\r\n () => import('./BaseTestChild2-WlFZNhyr.mjs').then(function(n) {\r\n return n.B;\r\n })\r\n );\r\n}\r\n```\r\nFor my part, when I remove the creation of this object to export in the same way as `.output/server/chunks/BaseTest-DrvCz1q7.mjs`, it works.\r\nOr if I add `n.B.default` to the `import('./BaseTestChild2-WlFZNhyr.mjs').then(function(n) {`, that works too.\n\n### Additional context\n\nTo reproduce, simply `yarn build` then `yarn preview` in my codesandbox example.\r\nYou can look directly at the existing `.output` that contains the problem.\r\nI don't know if this is the right place for this ticket or if I should make a ticket on the rollup side.\n\n### Logs\n\n_No response_",[2037],{"name":2005,"color":2006},27836,"Dynamic component SSR rendering problem","2024-08-12T21:15:06Z","https://github.com/nuxt/nuxt/issues/27836",0.6804711,{"description":2044,"labels":2045,"number":2049,"owner":1994,"repository":1994,"state":1995,"title":2050,"updated_at":2051,"url":2052,"score":2053},"\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.",[2046,2047,2048],{"name":2016,"color":2017},{"name":2005,"color":2006},{"name":2020,"color":2021},8579,"Client-only content doesn't render in component's slot","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8579",0.68106973,{"description":2055,"labels":2056,"number":2064,"owner":1994,"repository":1994,"state":1995,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25423\r\n\r\n### Describe the bug\r\n\r\nUsing nested slots in a server components + `nuxt-client` breaks:\r\n\r\nExample\r\n\r\n```vue\r\n\u003C!-- ServerComp.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CAppButton nuxt-client>\r\n \u003Cslot />\r\n \u003C/AppButton>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n\u003C!-- App.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CServerComp>\r\n Some slot content here\r\n \u003C/ServerComp>\r\n \u003C/div>\r\n\u003C/template>\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_",[2057,2058,2061],{"name":1985,"color":1986},{"name":2059,"color":2060},"🔨 p3-minor","FBCA04",{"name":2062,"color":2063},"server components","839413",25423,"Respect named slots in server components","2024-03-06T15:26:20Z","https://github.com/nuxt/nuxt/issues/25423",0.6827042,{"labels":2070,"number":2076,"owner":1994,"repository":1994,"state":1995,"title":2030,"updated_at":2077,"url":2078,"score":2079},[2071,2072,2075],{"name":1985,"color":1986},{"name":2073,"color":2074},"bug","d73a4a",{"name":2059,"color":2060},13117,"2023-01-19T16:57:45Z","https://github.com/nuxt/nuxt/issues/13117",0.6846603,{"description":2081,"labels":2082,"number":2086,"owner":1994,"repository":1994,"state":1995,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### 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_",[2083,2084,2085],{"name":1985,"color":1986},{"name":2059,"color":2060},{"name":2062,"color":2063},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.685577,{"labels":2092,"number":2096,"owner":1994,"repository":1994,"state":1995,"title":2097,"updated_at":2098,"url":2099,"score":2100},[2093,2094,2095],{"name":2016,"color":2017},{"name":2005,"color":2006},{"name":2020,"color":2021},8904,"Hydration error with scoped slots and component discovery (async components)","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/8904",0.686055,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"E2oF3VuYo4upRuf74SRT0MNp4b7soqNPAk7AiCivuAE":-1},"/nuxt/nuxt/15433"]