` doesn't print content correctly when loaded from SSR. If we trigger an HMR update, the content gets shown correctly.\r\n\r\nUsing a simple render function (as you can see in the reproduction) works correctly.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2926,2927],{"name":2904,"color":2905},{"name":2868,"color":2869},15218,"Dynamic component not rendering correctly when SSR","2023-01-19T17:46:17Z","https://github.com/nuxt/nuxt/issues/15218",0.6610623,{"labels":2934,"number":2937,"owner":2874,"repository":2874,"state":2908,"title":2938,"updated_at":2939,"url":2940,"score":2941},[2935,2936],{"name":2904,"color":2905},{"name":2868,"color":2869},13506,"\u003Ccomponent> seems to be broken.","2023-01-19T16:58:02Z","https://github.com/nuxt/nuxt/issues/13506",0.6636548,{"description":2943,"labels":2944,"number":2952,"owner":2874,"repository":2874,"state":2908,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Version\n\n[v2.9.2](https://github.com/nuxt.js/releases/tag/v2.9.2)\n\n### Reproduction link\n\n[https://github.com/raWINce/nuxt-async-loading-client-side-hydration](https://github.com/raWINce/nuxt-async-loading-client-side-hydration)\n\n### Steps to reproduce\n\n- in a component render html that depends on the viewport (e.g. using [`vue-mq`](https://github.com/AlexandreBonaventure/vue-mq) with `v-if=\"$mq === 'lg'\"`)\n- include those components as an [async component](https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components)\n- reload the page on a different viewport\n\n### What is expected ?\n\nDo not throw warning/errors after reloading the page (during client hydration).\n\nThe client hydration should work with async components, too, when using e.g. [nuxt-mq](https://www.npmjs.com/package/nuxt-mq)-dependent html.\n\n### What is actually happening?\n\nAfter reloading, the client hydration fails and throws `[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside \u003Cp>, or missing \u003Ctbody>. Bailing hydration and performing full client-side render.`.\n\nIn a more complicated setup this leads to an error that crashes the entire app (i.e. all components that are rendered later in the DOM do not work). I did not have time to make an example for this case, though\n\n### Additional comments?\n\n- Wrapping the component within `no-ssr` solves the issue. This, however, is not a solution for me because I need the html to be rendered on the server, which is the reason for choosing nuxt in the first place\n- including the component without dynamic import also solves the issue. \n - this makes me think that viewport dependent html can work with nuxt\n - hence, this is probably not a `nuxt-mq` issue\n\n\n\n\n\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9765\">#c9765\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2945,2948,2949],{"name":2946,"color":2947},"stale","ffffff",{"name":2868,"color":2869},{"name":2950,"color":2951},"2.x","d4c5f9",6403,"Client hydration fails with async components and breakpoint dependent html","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6403",0.66402733,{"description":2958,"labels":2959,"number":2962,"owner":2874,"repository":2874,"state":2908,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Environment\n\nclean setup on stackblitz\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ketx95?file=app.vue\r\n\r\n1. Please open devtools, \r\n2. Click any product on the list \r\n3. Notice there is two console.logs 'render' with two different instances of the same component. Described results on the video below: \r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/1b308d97-255d-435d-9d5b-439a2d049c1a\r\n\r\n\n\n### Describe the bug\n\n## Context\r\nWe use:\r\n+ dynamic page - `[...slug].vue`\r\n+ dynamic components - `component :is`\r\n\r\nScenario\r\n1. Fetch pageData on `[...slug].vue` by `useAsyncData`\r\n2. Render dynamic components based on `pageData`\r\n\r\n## A bug / a question? \r\nPlease click on some links in the product list (under \"Reproduction\").\r\nThe question is, why are components being rendered twice? This is causing unexpected bugs.\r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/1b308d97-255d-435d-9d5b-439a2d049c1a\r\n\r\nWe could prevent the double rendering by adding a :key to NuxtPage, but this would cause the page components to rerender before asyncData is resolved, which could have some impact. In this example, when we add :key, the components are only rendered once, but the page component is empty and does not wait for asyncData to render.\r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/f546fea4-3d03-41bb-b083-cc068a85bd50\r\n\r\nHow to prevent the effect of double rendering?\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2960,2961],{"name":2904,"color":2905},{"name":2868,"color":2869},20848,"Components are rendered twice (\u003Ccomponent :is> on [...slug].vue) ","2024-05-25T19:30:19Z","https://github.com/nuxt/nuxt/issues/20848",0.66717905,{"description":2968,"labels":2969,"number":2972,"owner":2874,"repository":2874,"state":2908,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Version\n\n[v1.4.2](https://github.com/nuxt.js/releases/tag/v1.4.2)\n\n### Reproduction link\n\n[https://codesandbox.io/s/oxp1oy83q?module=%2Fsrc%2FApp.vue](https://codesandbox.io/s/oxp1oy83q?module=%2Fsrc%2FApp.vue)\n\n### Steps to reproduce\n\n\n\n\n### What is expected ?\n\n\n\n\n### What is actually happening?\n\nwhen genarate (with or without ---spa),missing nested componet\n\n### Additional comments?\n\nonly when genarated file in `dist` ,ssr is fine\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7695\">#c7695\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2970,2971],{"name":2868,"color":2869},{"name":2950,"color":2951},3854,"genearted error with nested component","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3854",0.6719538,{"description":2978,"labels":2979,"number":2982,"owner":2874,"repository":2874,"state":2908,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Version\r\n\r\n[v2.8.1](https://github.com/nuxt.js/releases/tag/v2.8.1)\r\n\r\n### Reproduction link\r\n\r\n[https://codesandbox.io/s/themeable-nuxt-v2-1pcyw](https://codesandbox.io/s/themeable-nuxt-v2-1pcyw)\r\n\r\n### Steps to reproduce\r\n\r\n- Vistit URL, take note of styling\r\n- Click about\r\n- Click back home\r\n- You will see the client version renders correctly\r\n\r\n### What is expected ?\r\n\r\nServer version to render styles\r\n\r\n### What is actually happening?\r\n\r\nServer version skips styles\r\n\r\n\u003C!--cmty-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9504\">#c9504\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2980,2981],{"name":2868,"color":2869},{"name":2950,"color":2951},6084,"Async Loaded Components don't render Styles","2024-06-30T09:26:17Z","https://github.com/nuxt/nuxt/issues/6084",0.6719582,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNH7BRA1bxA5eY1j5gHBxrbOXgrVDFlT6W-vKg1aVDww":-1},"/nuxt/nuxt/5613"]