Hydration Error caused by chrome extension. #71577
-
Link to the code that reproduces this issuehttps://github.com/AlexanderHott/nextjs-15-chrome-extension-hydration To Reproduce
Current vs. Expected behaviorCurrently, there is a hydration error.
There shouldn't be a hydration error. I tried "disabling" the extension, but it still leaves the Provide environment informationOperating System:
Platform: linux
Arch: x64
Version: #47-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 21:40:26 UTC 2024
Available memory (MB): 15291
Available CPU cores: 16
Binaries:
Node: 21.4.0
npm: 10.2.5
Yarn: 1.22.22
pnpm: 9.12.2
Relevant Packages:
next: 15.0.0 // Latest available version is detected (15.0.0).
eslint-config-next: 15.0.0
react: 19.0.0-rc-65a56d0e-20241020
react-dom: 19.0.0-rc-65a56d0e-20241020
typescript: 5.6.3
Next.js Config:
output: N/A Which area(s) are affected? (Select all that apply)create-next-app Which stage(s) are affected? (Select all that apply)next dev (local) Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
Forgot to mention, this is on a clean create next app with all the defaults. |
Beta Was this translation helpful? Give feedback.
-
@AlexanderHott Moving this to discussions since this is expected with certain Chrome extensions. Unfortunately we can't do anything about this when it comes from a Chrome extension.
I would expect the extension to completely remove itself when disabled 🤔 |
Beta Was this translation helpful? Give feedback.
-
Try completely disabling the LanguageTool extention. This should solve this issue. (Checked, worked in my test.) |
Beta Was this translation helpful? Give feedback.
-
Getting this weird issue and i am using arc browser. -form_signature="7810705838526794697"
It can also happen if the client has a browser extension installed which messes with the HTML before React loaded. https://react.dev/link/hydration-mismatch
|
Beta Was this translation helpful? Give feedback.
There's a "disable" toggle in the extension itself. A workaround I found that works is (right click extension) > "This can read and change site data" > Select "When you click the extension".
If there is a way to disable it running on localhost, that would be great, but I haven't found one yet.