Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
v3 prop className did not match warning in Next.js
See original GitHub issueHi. I am seeing a warning since upgrading to version 3 with the latest versions of Next.js and React:
Warning: Prop className did not match. Server: "css-1g6gooi" Client: "css-w8afj7-Input"
See this sandbox for my reproduction: https://codesandbox.io/s/helloworld-g1mb7
Issue Analytics
- State:
- Created 4 years ago
- Reactions:38
- Comments:42 (1 by maintainers)
Top Results From Across the Web
Warning: Prop `className` did not match. when using styled ...
That error is showing you the class that is being created by your styled-components library on the server and how it is different...
Read more >Warning: Prop className did not match. #7322 - GitHub
The same happens with Next v.7. This error doesn't occur when the server starts, only after making changes in the code.
Read more >Solving the Styled Components Warning in Next.JS with Babel
Warning : Prop `className` did not match. Server: “fs-fdsf” Client: “sd-dfasj”. The combination of Next.JS and Styled Components is truly ...
Read more >Fixing ClassName did not match error - DEV Community
Warning : Prop `className` did not match. Server: Client: This is probably one of the most annoying problem with ...
Read more >Prop `className` did not match - CodeSandbox
Activating extension 'vscode.typescript-language-features' failed: Could not find bundled tsserver.js.
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
Fixed this with an update to some regex in emotion. An example of it working by reinstalling react-select so the new version of emotion is used: https://codesandbox.io/s/hello-world-jtyix
any movement on this im use Remix and have this same issues, I have added instanceId and InputId but still have this error with SSR
Warning: PropclassNamedid not match. Server: "css-b8ldur-Input"