-
-
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
Different classes on server and client when using css prop #2538
Comments
There's something weird going on with nextjs in dev mode (I see this in my projects as well), but the issue does not go through to production in my experience. |
Thanks for the reply @probablyup. So do you just ignore those warnings in development mode? The number of warnings goes up as I keep adding more |
Yeah I’ve just been ignoring them. We are removing that warning anyway so
don’t worry about it 👍
…On Sat, May 11, 2019 at 2:23 PM Gökhan Sarı ***@***.***> wrote:
Thanks for the reply @probablyup <https://github.com/probablyup>. So do
you just ignore those warnings in development mode? The number of warnings
goes up as I keep adding more css props and it is annoying :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2538 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAELFVUOJM3OAUHDZTOSM3LPU4MLTANCNFSM4HL7FVUQ>
.
|
/cc @timneutkens for visibility (not sure there's anything actionable for you to do here), this happens in my projects too. |
We don't really do anything weird here, just webpack HMR and re-rendering. Could you file an issue on Next.js so that I can add labels for people to look into it. |
@timneutkens Here it is: vercel/next.js#7322 |
@th0th this should be fixed with the latest babel plugin patch version, thanks for reporting! https://github.com/styled-components/babel-plugin-styled-components/releases/tag/v1.10.1 |
I get this warning when using styled-components 4.2.0 with next.js 8.
The only step needed to reproduce is to add something like this in a page on the default next.js example:
or
Here is a codesandbox:
https://codesandbox.io/embed/jlwvwyy0ow
https://jlwvwyy0ow.sse.codesandbox.io/
The text was updated successfully, but these errors were encountered: