\n \u003CNuxtPage /> \u003C!-- renders children like index.vue, favorite.vue -->\n \u003C/div>\n\u003C/template>\n```\n\nThis improves clarity by:\n\n* Explicitly distinguishing **nested layout files** from **page files**.\n* Avoiding the overloaded role of `parent.vue`.\n* Making folder structures self-explanatory.\n\n### Benefits\n\n* More intuitive project structure for large apps.\n* Easier onboarding for new developers (clear separation of layouts vs. pages).\n* Cleaner, scalable convention that aligns with the mental model of “global layouts” vs. “section layouts.”\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3137],{"name":3138,"color":3139},"pending triage","E99695",33073,"nuxt","open","[Enhancement] Better Syntax/Convention for Nested Layouts in Nuxt","2025-08-27T05:51:23Z","https://github.com/nuxt/nuxt/issues/33073",0.68872166,{"description":3148,"labels":3149,"number":3159,"owner":3141,"repository":3160,"state":3142,"title":3161,"updated_at":3162,"url":3163,"score":3164},"### Environment\n\nWin11, pnpm 10.8.0, node 23.11.0, vue/cli 5.0.8\n\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\nhttps://codesandbox.io/p/devbox/beautiful-hawking-xc35hk\n\n### Description\n\nIf I import `UIcon` and try to use it in a dynamic component, the app crashes. All the other nuxt/ui-components I tried work fine with this pattern. It works if I get the component-reference with `resolveComponent('UIcon')`, but it's very inconvenient for my actual use-case.. \n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport UIcon from '@nuxt/ui/components/Icon.vue';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003Ccomponent :is=\"UIcon\" v-bind=\"{ name: 'i-lucide-lightbulb' }\">\u003C/component>\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\nUncaught RangeError RangeError: Maximum call stack size exceeded\nat renderComponentRoot (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:6538:5)\n at componentUpdateFn (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5319:46)\n at run (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+reactivity@3.5.13\\node_modules\\@vue\\reactivity\\dist\\reactivity.esm-bundler.js:225:19)\n at setupRenderEffect (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5454:5)\n at mountComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5229:7)\n at processComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5182:9)\n at patch (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:4700:11)\n at componentUpdateFn (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5326:11)\n at run (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+reactivity@3.5.13\\node_modules\\@vue\\reactivity\\dist\\reactivity.esm-bundler.js:225:19)\n at setupRenderEffect (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5454:5)\n at mountComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5229:7)\n at processComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5182:9)\n at patch (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:4700:11)\n at componentUpdateFn (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5326:11)\n at run (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+reactivity@3.5.13\\node_modules\\@vue\\reactivity\\dist\\reactivity.esm-bundler.js:225:19)\n at setupRenderEffect (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5454:5)\n at mountComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5229:7)\n at processComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5182:9)\n at patch (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:4700:11)\n at componentUpdateFn (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5326:11)\n at run (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+reactivity@3.5.13\\node_modules\\@vue\\reactivity\\dist\\reactivity.esm-bundler.js:225:19)\n at setupRenderEffect (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5454:5)\n at mountComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5229:7)\n at processComponent (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:5182:9)\n at patch (d:\\Git\\TextTool\\ts-frontend\\src\\node_modules\\.pnpm\\@vue+runtime-core@3.5.13\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.esm-bundler.js:4700:11)\n...\n```",[3150,3153,3156],{"name":3151,"color":3152},"bug","d73a4a",{"name":3154,"color":3155},"v3","49DCB8",{"name":3157,"color":3158},"triage","ffffff",4571,"ui","UIcon component-reference in dynamic component causes stackoverflow","2025-07-22T17:14:49Z","https://github.com/nuxt/ui/issues/4571",0.6932832,{"description":3166,"labels":3167,"number":3172,"owner":3141,"repository":3141,"state":3173,"title":3174,"updated_at":3175,"url":3176,"score":3177},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.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@9.4.2\r\n- Builder: -\r\n- User Config: devtools, vue\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nYou can change the v-if from true to false to see the actual rendering failing:\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-gd1iaq?file=components%2FRichTextRenderer.vue\r\n\r\n### Describe the bug\r\n\r\nI am trying to render custom elements loaded from a CMS, example, I am trying to render responses like this:\r\n\r\n```\r\n\u003Cdiv>\r\n \u003Ccomponent :is=\"custom-element\">\u003C/component>\r\n \u003Ccomponent :is=\"custom-accordion\">\u003C/component>\r\n\u003C/div>\r\n```\r\n\r\nI was expecting to be able to do this by configuring the vue runtimeCompiler to true and using something like:\r\n\r\n```h({template: receivedHtml})```\r\n\r\n\r\n### Additional context\r\n\r\nOn the provided example, the three first options work, the fourth one fails:\r\n\r\n```\u003Cscript setup lang=\"ts\">\r\nconst CoolComponent = resolveComponent('CoolComponent')\r\n\r\nconst render1 = h({ template: '\u003Cspan>Hellow render 1\u003C/span>' })\r\nconst render2 = h({ template:`\u003Ccomponent :is=\"${CoolComponent}\">\u003C/component>` })\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cdiv>\u003Cb>Basic test:\u003C/b> \u003CCoolComponent>\u003C/CoolComponent>\u003C/div>\r\n\r\n \u003Cdiv>\u003Cb>Test without components:\u003C/b> \u003Crender1>\u003C/render1>\u003C/div>\r\n\r\n \u003Cdiv>\u003Cb>Test with component:\u003C/b> \u003Ccomponent :is=\"CoolComponent\">\u003C/component>\u003C/div>\r\n\r\n \u003Cdiv v-if=\"true\">\u003Cb>Broken test:\u003C/b> \u003Crender2>\u003C/render2>\u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n### Logs\r\n\r\n```shell-script\r\nmissing ] after element list\r\n\r\non esm-bundler.js\r\n```\r\n",[3168,3171],{"name":3169,"color":3170},"3.x","29bc7f",{"name":3138,"color":3139},24758,"closed","Unable to dynamically add components via string","2023-12-14T20:36:50Z","https://github.com/nuxt/nuxt/issues/24758",0.6507752,{"description":3179,"labels":3180,"number":3186,"owner":3141,"repository":3141,"state":3173,"title":3187,"updated_at":3188,"url":3189,"score":3190},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.15.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: pnpm@8.6.0\r\n- Builder: vite\r\n- User Config: extends, telemetry, ssr, nitro, fontMetrics, routeRules, runtimeConfig, build, modules, components, bugsnag, devtools, i18n, app, dnGraphqlClient, vite, plugins\r\n- Runtime Modules: @nuxtjs/fontaine@0.4.0, @pinia/nuxt@0.4.11, @nuxt/devtools@0.6.6, nuxt-bugsnag@5.9.2, @digitalnatives/css-variables/nuxt@5.1.0, @digitalnatives/graphql-client@3.2.2, @nuxtjs/i18n@8.0.0-beta.12\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nSetting up a component inheritance pattern:\r\n\r\n- With ssr: true...\r\n- Base component with a root-level `\u003Ccomponent>` element and one or more slots\r\n- An extending component which \"inherits\" the slots of the base component using `$slots` in the template;\r\n- Use the extending component somewhere\r\n- On the server, an error is thrown: `[1:54:29 PM] [Vue warn]: Property \"name\" was accessed during render but is not defined on instance.`\r\n- On the client, a hydration error is thrown: SSR renders no content within the slots, client-side the component is rendered correctly however\r\n\r\nSee https://codesandbox.io/p/github/nuxt/starter/csb-rhhp8s/draft/determined-joliot?file=/app.vue:3,69\r\n\r\n### Describe the bug\r\n\r\nIt seems server-side there is some problem with SSR trying to pass slots to a dynamic `\u003Ccomponent>`\r\n\r\nI would expect this pattern to work, but somehow the slot name is getting lost somewhere\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Ccomponent\r\n :is=\"element\"\r\n >\r\n \u003Cslot />\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_",[3181,3182,3183],{"name":3169,"color":3170},{"name":3138,"color":3139},{"name":3184,"color":3185},"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":3192,"labels":3193,"number":3196,"owner":3141,"repository":3141,"state":3173,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### 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",[3194,3195],{"name":3169,"color":3170},{"name":3138,"color":3139},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":3202,"labels":3203,"number":3211,"owner":3141,"repository":3141,"state":3173,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### 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_",[3204,3205,3208],{"name":3169,"color":3170},{"name":3206,"color":3207},"🔨 p3-minor","FBCA04",{"name":3209,"color":3210},"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":3217,"number":3224,"owner":3141,"repository":3141,"state":3173,"title":3225,"updated_at":3226,"url":3227,"score":3228},[3218,3221],{"name":3219,"color":3220},"enhancement","8DEF37",{"name":3222,"color":3223},"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":3230,"labels":3231,"number":3234,"owner":3141,"repository":3141,"state":3173,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### 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_",[3232,3233],{"name":3169,"color":3170},{"name":3138,"color":3139},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":3240,"labels":3241,"number":3252,"owner":3141,"repository":3141,"state":3173,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### 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_",[3242,3243,3244,3246,3249],{"name":3169,"color":3170},{"name":3138,"color":3139},{"name":3245,"color":3207},"needs reproduction",{"name":3247,"color":3248},"layers","006B75",{"name":3250,"color":3251},"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":3258,"number":3261,"owner":3141,"repository":3141,"state":3173,"title":3262,"updated_at":3263,"url":3264,"score":3265},[3259,3260],{"name":3138,"color":3139},{"name":3222,"color":3223},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,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJa4zmPr-4FRXWGTnBZpAG9noQwEpXtJtYo3J1ax-sHA":-1},"/nuxt/ui/4138"]