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.
Inconsistent CSS between dev and build
See original GitHub issueBug report
Describe the bug
When using the “Built-in CSS support”, the ordering of the CSS classes (and number of times a class is declared) is not consistent between development and production.
Because of this, you can see some CSS styling “pop” around when navigating between pages.
I believe the order is correct in SSR, but not in the client-side loaded bundles (as more CSS is loaded asynchronously, the ordering is lost and duplicated styles are loaded)
To Reproduce
Just run next build, the issue seems to be out-of-the-box with CSS modules?
Expected behavior
The resulting CSS styles ordering should be identical between dev and prod.
Screenshots
Dev: (Desired behaviour):
Build: (Duplicated styles, inconsistent result:)
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can you try next@canary? Many issues with CSS / ordering of CSS were solved recently.
Please open a new issue with a full reproduction.