-
Notifications
You must be signed in to change notification settings - Fork 48
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
React attempted to reuse markup in a container but the checksum was invalid. #19
Comments
This package doesn't support React 15 yet... |
Yeah, sorry for the delay, I've been hard at work trying to lay the groundwork for integrating streaming into react core. As of now, If my PR doesn't go through, I'll re-evaluate how best to support streaming going forward. Thanks for your engagement, and please let me know if you have any questions or comments! |
So is it safe to assume this package will never support React 15? |
Hi @aickin. Great job really ! I had similar problems with this project. I already read (after some time spent) that React already supports streams in version 16+. Could you update the read.me on the beginning with the compatibility of this project with React versions and a line saying this project is not needed anymore pointing to your article ? I think that would help a lot of people, if they stumble upon this project first like me. Big thanks |
Hi guys,
I was making a small POC with the stream SSR, and React seems to be complaining about the checksum while reattaching the DOM.
Just wanted to know if I'm doing something wrong or this is just a version difference between the react-dom-stream fork and react-dom.
This is the warning from React:
This is the code I've used to attach the client in both tests:
This is what gets rendered with the original React DOM:
The code that renders it:
This is what gets rendered with react-dom-stream:
and the code that renders it:
Here are my dependencies:
Let me know if I can help with something and thanks for the great work Sasha,
Sam.
The text was updated successfully, but these errors were encountered: