i think row components cause diffrent style between server & client when i using next.js
See original GitHub issue- I have searched the issues of this repository and believe that this is not a duplicate.
Reproduction link
https://github.com/SimDaeSoo/Sample
Steps to reproduce
- yarn
- yarn dev
- look chrome developer tools console
What is expected?
i think row components cause diffrent of ssr and csr
how can i remove this error log?
What is actually happening?
at SSR Row
components has no row-gap style.
because SSR didn’t pass detectFlexGapSupported
condition.
but Client Row
components has row-gap style.
Environment | Info |
---|---|
antd | 4.12.2 |
React | 17.0.1 |
System | macOS Big Sur 11.1(20C69) |
Browser | chrome 88.0.4324.96 (x86_64) |
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Rendering: Server and Client Components - Next.js beta docs
This page will go through the differences between Server and Client Components and how to use them in your Next.js application.
Read more >Fun With Next.js 13 Server Components - DEV Community
I.e., the rendering happens and only happens on the server side, even if the loading of the component is triggered on the client...
Read more >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 >Next.js: The Good, Bad and Ugly - An Idiosyncratic Blog
Server -Side Rendering - Being able to pre-render React components on the server side, before sending the HTML to the client is a...
Read more >Using LaunchDarkly with Next.js
Client -side rendering: Some content, such as user-specific data on a pre-rendered page, cannot be fully rendered before deployment. In these ...
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
The break was introduced with version
4.12.0
by this PR.Reverting to
4.11.3
seems to fix it.I still face the same problem in the later version, will it be fixed? It causes us trouble because the style between the development environment and the SSR build version is different.