nuxt: [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, or missing . Bailing hydration and performing full client-side render.

| 0down votefavorite | [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, or missing . Bailing hydration and performing full client-side render. – | – | –



<template lang="pug">
    div
      header
       h1 project news line
       nav
        nuxt-link(to='/') home
        nuxt-link(to='/about') about 
        nuxt-link(to='/contacts') call me
      .wrapper
       form(@submit="postMesseage")
        section.container
         md-input-container
          label With label
          md-input(placeholder='Head',  v-model="name", type='text', )

          button(type="submit") add news
         .quill-editor(:content='content', @change='onEditorChange($event)', @blur='onEditorBlur($event)', @focus='onEditorFocus($event)', @ready='onEditorReady($event)', v-quill:myquilleditor='editorOption', v-model="newMessage")

       section#message(v-for='(message, index) in messages')

         button( @click="deleteRow(index)" v-bind:id="message._id") удалить
         nuxt-link(:to="{ path: '/edite/'+message._id,  params: { id: message._id } }") 
          button Редактировать
         h2 
          nuxt-link(:to="{ path: '/news/'+message._id,  params: { id: message._id } }" ) {{ message.name }}

           div(v-html="message.content") {{ message.content }}




    </template>

how fix it ? not understand 😦 help please

<div align="right">This question is available on Nuxt.js community (#c1397)</div>

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 20

Most upvoted comments

@andysay this is to do with a component not being compatible with ssr, use <no-ssr></no-ssr> to wrap the troublesome component and hide the error.

not bailing on this @qm3ster just wrapped up in work tonight! will report back soon, moving the <no-ssr> tags as requested for a test.

I see it’s really static inside, okay. Okay, so, probably won’t help, but start by relocating that somewhere else, for example ~/assets, or anywhere non-special. You are requiring it into the bundle, so absolutely no reason for static to copy that into your dist.