[mini-css-extract-plugin] Conflicting order between:
See original GitHub issue- I have searched the issues of this repository and believe that this is not a duplicate.
Reproduction link
Can’t reproduce
Steps to reproduce
During build process react-create-app
I receive warnings regarding Conflicts order between
styles in antd lib
What is expected?
What is actually happening?
chunk 3 [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--7-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./node_modules/antd/lib/empty/style/index.css
* css ./node_modules/css-loader??ref--7-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./node_modules/antd/lib/select/style/index.css
Environment | Info |
---|---|
antd | 3.15.2 |
React | ^16.8.2 |
System | Ubuntu 16.04 |
Browser | Not related to browser |
Could you please fix/sort your styles
Issue Analytics
- State:
- Created 4 years ago
- Reactions:15
- Comments:68 (6 by maintainers)
Top Results From Across the Web
mini-css-extract-plugin throws "Conflicting order" errors during ...
Same as in this issue I am getting a lot of errors from the mini-css-extract-plugin when doing a CI build - which fails...
Read more >How do I avoid the warning: chunk styles [mini-css-extract ...
However, I'm receiving the following message when I use gatsby build . warn chunk styles [mini-css-extract-plugin] Conflicting order. Following ...
Read more >Fix warn chunk commons [mini-css-extract ... - Robert Marshall
This error/warning is caused by the Webpack plugin mini-css-extract-plugin wanting all CSS imports to be in the same order. This is because it ......
Read more >WebPack - mini-css-extract-plugin - Dirask
I use import style from './style.scss' to attach styles to components. Is there some way to order styles in the correct way? Webpack...
Read more >mediacurrent/gatsby-plugin-silence-css-order-warning
The webpack mini-css-extract-plugin however, still warns that the CSS might be bundled out of order. The warning is: warn chunk styles [mini-css-extract-plugin] ...
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
Is there any certain way to fix this? I’m using Next.js + Ant Design and I see a lot of warnings like this.
Also, pages sometimes don’t display properly. I think it is because of this conflict error.
+1 on using with Next.js!