You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when processing our application, ember-css-modules, concats all the *.css files into a single file. This includes app/styles/*.css. Unfortunately, it seems to do it in whatever order it wants and with regards to things like @import. Thus we end up with an output file that has all of our component css files at the top and our app/styles/*.css at the bottom, apparently in alphabetical order. such that app.css comes before reset.css, which is problematic.
And headerModules doesnt seem to have an impact.
And importing via @import statements just lands us two copies of the css file being included.
So, unless we're doing something wrong, I think we need a way to control what files ember-css-modules includes and possibly in what order they are included.
Currently when processing our application, ember-css-modules, concats all the *.css files into a single file. This includes
app/styles/*.css
. Unfortunately, it seems to do it in whatever order it wants and with regards to things like@import
. Thus we end up with an output file that has all of our component css files at the top and ourapp/styles/*.css
at the bottom, apparently in alphabetical order. such thatapp.css
comes beforereset.css
, which is problematic.And
headerModules
doesnt seem to have an impact.And importing via
@import
statements just lands us two copies of the css file being included.So, unless we're doing something wrong, I think we need a way to control what files ember-css-modules includes and possibly in what order they are included.
Our config, for reference:
@optikalefx
The text was updated successfully, but these errors were encountered: