\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_",[2868,2869,2870],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2871,"color":2872},"upstream","E8A36D",21915,"Hydration error for slot \"inheritance\" on dynamic components","2023-07-25T06:43:06Z","https://github.com/nuxt/nuxt/issues/21915",0.6513799,{"description":2879,"labels":2880,"number":2883,"owner":2859,"repository":2859,"state":2860,"title":2884,"updated_at":2885,"url":2886,"score":2887},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v16.19.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: pnpm@8.9.2\r\n- Builder: -\r\n- User Config: devtools, vite\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-yfh8fb?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nVue Router's link component exposes its api via v-slot api as noted here https://router.vuejs.org/guide/advanced/composition-api.html#useLink which I have used in a vue 2 component. But after migrating to Vue 3 and attempting to use the same component in a Nuxt 3 application, it does not work because nuxt does not offer the v-slot api, resulting in a destructuring error. \r\n\r\n**NOTE: this is only an issue when using dynamic components it seems. Adding `custom` to a regular NuxtLink component works just fine.**\r\n\r\nThe component I have is meant to support both vue router and nuxt router, which means it must work for both router-link and nuxt-link. This is now an issue because nuxt 3 does not provide the v-slot api. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nCannot destructure property 'href' of 'undefined' as it is undefined.\r\n\r\nat Proxy.renderFnWithContext (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:770:13)\r\nat Proxy.eval (./node_modules/nuxt/dist/app/components/nuxt-link.js:260:92)\r\nat renderComponentRoot (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:830:16)\r\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:702:28)\r\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:631:12)\r\nat Module.ssrRenderComponent (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:86:10)\r\nat _sfc_ssrRender (./app.js:28:31)\r\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:685:9)\r\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:631:12)\r\n```\r\n",[2881,2882],{"name":2853,"color":2854},{"name":2856,"color":2857},24874,"Nuxt link does not expose slot api on dynamic components","2024-01-03T20:23:21Z","https://github.com/nuxt/nuxt/issues/24874",0.67162585,{"description":2889,"labels":2890,"number":2898,"owner":2859,"repository":2859,"state":2860,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### 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_",[2891,2892,2895],{"name":2853,"color":2854},{"name":2893,"color":2894},"🔨 p3-minor","FBCA04",{"name":2896,"color":2897},"server components","839413",25423,"Respect named slots in server components","2024-03-06T15:26:20Z","https://github.com/nuxt/nuxt/issues/25423",0.67324764,{"labels":2904,"number":2911,"owner":2859,"repository":2859,"state":2860,"title":2912,"updated_at":2913,"url":2914,"score":2915},[2905,2908],{"name":2906,"color":2907},"enhancement","8DEF37",{"name":2909,"color":2910},"2.x","d4c5f9",6668,"Proposal to replace \u003Cnuxt> and \u003Cnuxt-child> by normal slots","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6668",0.6771346,{"description":2917,"labels":2918,"number":2921,"owner":2859,"repository":2859,"state":2860,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.13`\r\n- Nitro Version: `0.6.1`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `build`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-rhmame-yu2hri?file=components%2FNestedSlots.vue,app.vue\n\n### Describe the bug\n\nThis is a weird one, it is probably easier to understand looking at the reproduction example.\r\n\r\nWhen defining slot content / templates in a `v-for` loop, the current loop element is undefined in that slot. However, this only occurs in very specific cases:\r\n\r\n1. Page is rendered in SSR\r\n2. Slot Templates are defined in `v-for`\r\n3. Content referencing the loop element is using an external component that is also using slots\r\n\r\nIt works perfectly fine on client side or if the component used to render the content is internal (part of the same project, not pre-built from a library).\n\n### Additional context\n\nWe came across this issue when starting to extract a component library from our project prototype.\r\n\r\nWe have a dynamic table / listing component used to render a list of objects based on a column configuration. This component also provides dynamic scoped slots for every column in case we want to customize the rendering.\r\n\r\nUnder the hood, it uses our basic table components to render table rows and cells. After we moved those table components to our new component library, the dynamic listing suddenly broke in SSR.\r\n\r\nHowever, I made the reproduction example as simple as I could and used a random UI library instead of our own code to make sure the same error happens.\n\n### Logs\n\n_No response_",[2919,2920],{"name":2853,"color":2854},{"name":2856,"color":2857},15433,"Loop context is lost when rendering nested slot in v-for using external component in SSR","2023-01-19T17:50:15Z","https://github.com/nuxt/nuxt/issues/15433",0.67938113,{"description":2927,"labels":2928,"number":2939,"owner":2859,"repository":2859,"state":2860,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.8.0\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@9.7.2\r\n- Builder: vite\r\n- User Config: ssr, srcDir, devtools, extends, vite, modules, graphql-client, app\r\n- Runtime Modules: vuetify-nuxt-module@0.5.7, nuxt-gtag@0.5.9, nuxt-graphql-client@0.2.30\r\n- Build Modules: -\n\n### Reproduction\n\nHave your main App with:\r\n```\r\nexport default defineNuxtConfig({\r\n extends: [\r\n './layers/my_awesome_layer',\r\n ],\r\n})\r\n```\r\n\r\nHave a simple page doing something like:\r\n```\r\n\u003Ctemplate>\r\n \u003CTheNavbar />\r\n\u003C/template>\r\n```\r\n\r\nWith the component TheNavbar being in your layer.\r\nIf I add\r\n```\r\n components: {\r\n dirs: [\r\n {\r\n path: '~/components/global',\r\n global: true,\r\n },\r\n '~/components',\r\n ],\r\n },\r\n```\r\n\r\nIn the config of my layer so I can use `\u003Ccomponent :is=\"resolveComponent('TheNavbar')\" />`\r\n\r\n\n\n### Describe the bug\n\nThe overall problem is that I have an UI-Kit layer with a lot of components.\r\nAnd in my pages I must call an external API with fetch to retrieve an array of components.\r\nThen I have to use the dynamic \u003Ccomponent :is /> but when I try to globally register my layer components it does not work at all and even when it's not dynamic those layer components are unkwown.\r\n\r\nSo is it a bug?\r\n\r\nWhat would be the best practice to have dynamic component with name fetched from an external API on a page and with all of them registered in a layer?\r\n\r\nThank you all!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2929,2930,2931,2933,2936],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2932,"color":2894},"needs reproduction",{"name":2934,"color":2935},"layers","006B75",{"name":2937,"color":2938},"closed-by-bot","ededed",22704,"Marking Layer Components Global = Failed To Resolve","2023-09-07T01:47:44Z","https://github.com/nuxt/nuxt/issues/22704",0.6829531,{"labels":2945,"number":2948,"owner":2859,"repository":2859,"state":2860,"title":2949,"updated_at":2950,"url":2951,"score":2952},[2946,2947],{"name":2856,"color":2857},{"name":2909,"color":2910},8379,"Functional components not worked if import dynamically with SSR context","2024-06-30T09:25:57Z","https://github.com/nuxt/nuxt/issues/8379",0.68348175,{"description":2954,"labels":2955,"number":2961,"owner":2859,"repository":2859,"state":2860,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### 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",[2956,2957,2958],{"name":2853,"color":2854},{"name":2871,"color":2872},{"name":2959,"color":2960},"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.68605775,{"labels":2967,"number":2970,"owner":2859,"repository":2859,"state":2860,"title":2971,"updated_at":2972,"url":2973,"score":2974},[2968,2969],{"name":2856,"color":2857},{"name":2909,"color":2910},4960,"Dynamic component server side rendering doesn't work when used inside v-if and v-else","2024-06-20T14:03:01Z","https://github.com/nuxt/nuxt/issues/4960",0.6868235,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJa4zmPr-4FRXWGTnBZpAG9noQwEpXtJtYo3J1ax-sHA":-1},"/nuxt/ui/4138"]