-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
create-remix@latest results in hydration errors on unmodified build #5416
Comments
OK, I think I figured this one out |
Sorry I should have included I was on chrome. I also had that extension and disabling it indeed seems to have fixed this issue. Nice find! Is this an issue with the extension then? |
Mind. Blown. 🤯 Sorry for the spam, but thanks SO MUCH! That extension caused me hours of looking through the code why stuff would be different. |
This issue has been seen before - there's a proposal about it here: #5244 |
Had this issue happening with the Meteor devtools extension too (Chrome 111). |
Same issue, disabling all extensions fixed it, I'm guessing the scripts injection of extensions caused this? pnpm create remix@latest
# node v18.15.0
# Brave 1.50.114 Chromium: 112.0.5615.49 (arm64) |
I believe this is a duplicate of the #5244 and will be (hopefully) addressed when React 18.3 is released. See facebook/react#24430 (comment) for more information. I'm going to close this out as there's not much Remix can do it seems. |
What version of Remix are you using?
1.12.0
Are all your remix dependencies & dev-dependencies using the same version?
Steps to Reproduce
Then:
Repro: https://github.com/wulfmann/remix-repro
Expected Behavior
A fresh bare build does not log hydration errors.
Actual Behavior
Hydration errors are logged complaining about a missing closing
<head>
tag.The text was updated successfully, but these errors were encountered: