-
Notifications
You must be signed in to change notification settings - Fork 17
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
False positives with MUI library #13
Comments
It looks like MUI renders inline styles in SSR, but uses classnames in CSR, which causes this mismatch. Not sure how to approach hiding these false positives... 🤔 |
Actually: could you provide the full diff here? Before and After? It looks like the left side has a big Emotion <style> tag: we could potentially remove those from the SSR to simplify things...although the hydration mismatch could potentially be IN the emotion tag too 😅 |
Here is the BUILDER_HYDRATION_OVERLAY object. BUILDER_HYDRATION_OVERLAY object.json If the problem is with the emotion tag, I should have the problem first too, right? |
If by "first" you mean "before using this hydration overlay", then no. The reason we get false positives is explained here: https://github.com/BuilderIO/hydration-overlay/?tab=readme-ov-file#caveats |
I'm using Next.js (v13 with pages directory) with the MUI library. In the case of error Hydration, it's hard to debug compared to native modal error and seems not to have the same value.
Here is an example. I just added
Math.random()
The text was updated successfully, but these errors were encountered: