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.

Inconsistent loading order of CSS in dev mode

See original GitHub issue

Bug report

Describe the bug

It’s based on https://github.com/zeit/next.js/issues/10148#issuecomment-614478653. When _app.jsx contains component which imports postcss module the order of css chunks is inconsistent. Most likely css from module is inserted before global css.

To Reproduce

I created a repo for you https://github.com/Joozty/nextjs-css. It’s a fork from https://github.com/zeit/next.js/issues/10148. So the steps to reproduce are almost identical.

Expected behavior

CSS in dev mode should be imported/inserted the same way as on production, i.e. global css first and then modules.

Thanks a lot 😃

Issue Analytics

State:
Created 3 years ago
Reactions:7
Comments:16 (2 by maintainers)

Top GitHub Comments

4reactions

fabinppkcommented, Apr 22, 2020

This should be fixed in ^9.3.6-canary.9!

I’m installed the exact version 9.3.6-canary.9 and unfortunately in production mode there are still duplicate css.

I’m using sass, but I don’t think that could be the problem.

3reactions

iksentcommented, Apr 23, 2020

Yes, my problem has not been resolved either. Should we open a new issue, @Timer? Or maybe move to there: https://github.com/zeit/next.js/issues/12099