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
Conflicting order in css modules causes failed CI #325
Comments
Did that happen on a fresh unmodified copy of this template? I've seen this kind of conflict a couple of times when the import order of certain files/modules is not fixed. E.g. have you added Styleguide examples? Those examples might reveal that the CSS imports of child components are not always following the same order, which then throws this warning. |
I've figured out the issue - I create two new panel components (EditListingAboutPanel and EditListingSpecsPanel), and I had them imported in
The issue seems to be that I was importing the |
This is a pretty good description on how to debug these: |
Closing this - as the issue seems to be resolved for now. |
Description
When trying to run
yarn build
, Mini CSS throws a warning regarding the order of CSS modules. In a CI process, this causes the run to fail unlessprocess.env.CI
is set tofalse
(which is not ideal behaviour).To Reproduce Steps to reproduce the behavior:
yarn build-web
Expected behavior
The CSS modules should build without warnings.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
I am using GitHub Actions to product my build. Simple workflow script that installs and builds the template
The text was updated successfully, but these errors were encountered: