Fetch in component causes hydration to fail if page also has async fetchnuxt/nuxt · closed3 years ago · 39% similar stalepending triage2.x
Client hydration fails with async components and breakpoint dependent htmlnuxt/nuxt · closed3 years ago · 39% similar stalepending triage2.x
Nested NuxtLink/RouterLink components break SSR and throw a hydration mismatchnuxt/nuxt · closed2 years ago · 39% similar 3.xpending triage
Hydration error for slot "inheritance" on dynamic componentsnuxt/nuxt · closed2 years ago · 38% similar 3.xpending triageupstream
Hydration of components with fetchHook in the layout scope will failnuxt/nuxt · closed3 years ago · 38% similar pending triage2.x
mismatch server-rendered content when filling the store in the nuxtServerInitnuxt/nuxt · closed3 years ago · 38% similar 2.x
[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 <p>, or missing <tbody>. Bailing hydration and performing full client-side render.nuxt/nuxt · closed3 years ago · 37% similar documentation2.x
async server components are not rendered in initial HTMLnuxt/nuxt · closed3 years ago · 37% similar 3.xbugupstream🔨 p3-minorupstream-bug
Using defineNuxtComponent and components:false causes hydration mismatches errornuxt/nuxt · closed3 years ago · 37% similar 3.xpending triage