I build an isomorphic react app and some time a meta tag is not self closing on the server side, and i have the following invalid checksum error :
You're trying to render a component to the document using server rendering but the checksum was invalid. This usually means you rendered a different component type or props on the client from the one on the server, or your render() methods are impure. React cannot handle this case due to cross-browser quirks by rendering at the document root. You should look for environment dependent code in your components and ensure the props are the same client and server side:
(client) -8" data-reactid="3"/><meta http-equiv="
(server) -8" data-reactid="3"><meta http-equiv="X
Is there a way to avoid this? any ideas ?
Assuming the keys are identical (which they seem to be) this was a known issue in the 0.13.* versions. Ensuring both react and react-dom packages are both at least 0.14.0 you should be good.
Related
I created server side rendering with approach described in redux's official site, everything is great, but on client side it rendering components again, and this is not good I think. I am passing same state from server to window.__STATE__ variable and passing this to my client side createStore method as initial state, but it rerendering again.
Also please write in comments which part of code is needed to you, if so.
I am not providing since it is very similar to official page instructions code and there is no errors, just issue with rerendering, but as I understand it is not connecting to virtual DOM.
Please help me find valid way for handling this task.
Take a look at this example from the ReactGo project: https://github.com/reactGo/reactGo/blob/master/app/client.jsx#L22
They use a function onUpdate that has the conditional
if (window.__INITIAL_STATE__ !== null) {
window.__INITIAL_STATE__ = null;
return;
}
which prevents a duplicate fetches if __INITIAL_STATE__ is already defined. Your components rerendering may have something to do with the duplicate fetching.
Perhaps I am not understanding what you mean by re-rendering, but it is supposed to "re-render" on the client again. The way isomorphic works is that it renders the HTML on the server, and then the payload includes the initial state as well has the HTML markup - this way the browser "appears" to have faster page load times - since the UI is rendered even before the script is executed. Now once the HTML parsed and the script runs, React internally builds the virtual DOM and then compares it to the server generated DOM and wires up event listeners etc. It does not however, do a full re-render in that no new DOM elements should be created. If for any reason the client run of your React render results in a virtual DOM that is different from the generated server DOM, React will give you a warning.
"Warning: React attempted to reuse markup in a container but the
checksum was invalid. This generally means that you are using server
rendering and the markup generated on the server was not what the
client was expecting. React injected new markup to compensate which
works but you have lost many of the benefits of server rendering.
Instead, figure out why the markup being generated is different on the
client or server:"
I am new to React and Redux . Although i know that React is just a view layer . But i saw a term "React can be used on server side rendering". What does this mean and how it works behind the scene with nodejs.Can anyone help me in getting clear the fact that "What is server side render in react".
The react-dom package includes a server module. This module allows you render your react application to a simple HTML string with reactDOMServer.renderTostring(). Basically a snapshot of your view for a given set of props:
https://facebook.github.io/react/docs/top-level-api.html#reactdomserver.rendertostring
Additionally this functions calculates a unique hash from the string it generated and appends it to the html. On the client side react can "pick up" the server generated HTML and use it as its "first render".
Though the client side first render and the server render need to produce the exact same output for react to pick it up on the client side. React can check this via the generated hash: The client side react will also generate a html string (without modifying the actual DOM, I think this is done only on the virtual DOM). Now it can also calculate a hash from its virtual DOM and compare it with the server rendered one. If they match, no rendering needs be done. If they don't, the client side react will throw away the server generated DOM and replace it with its version (and print out an error/warning).
In combination with redux this means in addition to rendering the HTML you need to pass down the state of your store (store.getState()) to the client. The client can then use this serialized state as an initial state when creating its instance of the redux store. This will lead to both renders (client + server) to match up.
If you don't need the client side to do anything and just want to create static markup on the server side, react-dom offers a renderToStaticMarkup() function:
https://facebook.github.io/react/docs/top-level-api.html#reactdomserver.rendertostaticmarkup
I have window dependency in some of modules I use, so I cannot render part of my app on a server. However the content send from a server should be the same as a content rendered on a client first time, otherwise there will be a: "React attempted to use reuse markup in a container but the checksum was invalid" warning.
Seems like I need to do some workaround, render the content from a server and then, after component is mounted, render a client only part. Similar issue described here.
I feel this is the best solution, however eslint from AirBnB throws an error that changing state in componentDiMount is not good.
Do you have better ideas?
I have a file upload component.
IE8: Using iframe for file upload.
Chrome: Using FormData
When doing server rendering, iframe is created in HTML.
When Chrome loads the page, there's no iframe.
So the waring is caused: Warning: React attempted to reuse markup in a container but the checksum was invalid
My question: How to handle this case?
You can fix this. Whether or not you should is another question...
Whatever it is that's putting the <iframe> in the page (or not) is doing so before React is running its first render cycle. You can prevent this (and anything else that modifies the DOM) in your main components componentDidMount() method.
There is a more complex approach of getting the userAgent string on the server and rendering appropriately there (Radium does this).
However, that warning is harmless. It is not shown with the production (minified) version of React so only affects the development experience. In my opinion I'd say leave it as is rather than push more complex code into production because of a warning in development. Maybe just try and get the server to default to not doing the iFrame.
I'm reading this example of React server-side rendering. It states:
Try viewing the page source to ensure the HTML being sent from the server is already rendered (with checksums to determine whether client-side rendering is necessary)
Ok, I saw page source and there is indeed a data-react-checksum attribute:
<div data-reactid=".157rq30hudc" data-react-checksum="556954499">
And when I check the element in a browser console, it also has the attribute:
Then I decided to checked my site that uses React server side rendering too. And I see strange thing. Page source has data-react-checksum attribute but the element is a console doesn't.
Page Source:
<div class="activityOptionBox" data-reactid=".1l6uko4wt8g" data-react-checksum="168103090">
Console:
What does it mean? What for checksum and how to read/use it?
The checksum is used internally by React on the client, when using server rendering via ReactDOM.renderToString, to determine if the output from the server matches the output from the client. If it does, React can transparently upgrade the existing DOM from the server into a client-side app very efficiently. If it doesn't match, it means that the state and props to render on the server were different from the state and props to render on the client, and React must do a more expensive operation to initialize the client-side app.
I checked an app of mine, and it seems that—in at least some versions of React—the checksum attribute is removed from the element once the client-side application boots, though it is visible in the source code of the page.
Since the checksum is an internal consistency mechanism, you don't need to worry about it unless React detects that your server checksum and client checksum don't match, in which case it'll tell you via a warning or error in the console.