Server Side Rendering Support on v1.6
See original GitHub issueHello,
I am facing issue for server side rendering using react-burger-menu version 1.6.
Here’s the warning:
warning.js?0260:45 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: (client) ition:opacity 0.3s, transform 0s 0.3s;" (server) ition:opacity 0.3s, -ms-transform 0s 0.3
@negomi
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
React v16 ServerSide Rendering - Toru Kobayashi - Medium
To do that, you need to generate HTML, added a checksum and some attributes, from App Component and embed it in Html Component...
Read more >How to Enable Server-Side Rendering for a React App
In this tutorial, you will initialize a React app using Create React App and then modify the project to enable server-side rendering.
Read more >Top 7 React JS V16 Released Features - Ficode
4. Server Side Rendering. React V16 supports streaming which is a complete server renderer. It works very fast which helps you to send...
Read more >Using Server-side Rendering (SSR) - Gatsby
Server -side Rendering (SSR) is one of Gatsby's rendering options and allows you to pre-render a page with data that is fetched when...
Read more >Frequently Asked Questions - Loadable Components
Can I use Loadable Components with server-side rendering of React on top of Ruby on Rails? ... Yes. It works with React on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@negomi ok installed last version and its working
Ok, tried a slightly different setup and I managed to get the error.
I’ve just pushed a release (v1.8.1) which fixes it. Please let me know if it’s still a problem 😃