-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The client-side rendered virtual DOM tree is not matching server-rendered content. #45
Comments
Please provide some information. ...what did you do to mak this happen? Did you change anything or did you run the original code? If the latter, on what node version is the server running? What Browser did you use? |
@LinusBorg I think so firebase automatically updated realtime. |
I am getting this error on a fresh install. It doesn't happen on first load, but just doing a full refresh in the browser and I get this error in dev tools. Anyone find a solution? |
Also, I only see this error when running in dev mode. Production seems to be fine. |
I have this issue on my current Vue project (I'm using the "prefetch" methods approach shown here for SSR). It looks like Vuex actions are invoked on initial render, but then we get this error because the actions haven't commited state yet, so our vdom list is empty compared to the server-rendered html. I don't see how they are supposed to match, so wondering why there is a warning for this at all. Also wondering if hydration is scrapped for the entire app or just this particular component, and if the former, does it do this in production? |
I also encountered this problem, how do you solve the problem? |
I also have this issue during ssr when rendering elements whose if statements are coming from a vuex getter |
nvm just saw this @corner1990 |
Hi ,
I saw an error like this
The text was updated successfully, but these errors were encountered: