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
In a classic build, my addons css was being concatenated into vendor.css in alphabetical order based on package name, which I think is a result of file system behavior once their individual processed css files are merged into a folder.
With embroider, I'm getting a very different order that I don't fully understand. I tried using package.json "ember-addon"."before"/"after" config which didn't seem to have any impact.
I have a very large monorepo with ~100 addons, so migrating fully off of implicit styles would be a large effort. But with the changed css order we've found issues where same-specificity rules changed order and a different one is taking precedence with embroider than with classic.
Is there any way to control the order that I'm missing?
The text was updated successfully, but these errors were encountered:
In a classic build, my addons css was being concatenated into vendor.css in alphabetical order based on package name, which I think is a result of file system behavior once their individual processed css files are merged into a folder.
With embroider, I'm getting a very different order that I don't fully understand. I tried using package.json "ember-addon"."before"/"after" config which didn't seem to have any impact.
I have a very large monorepo with ~100 addons, so migrating fully off of implicit styles would be a large effort. But with the changed css order we've found issues where same-specificity rules changed order and a different one is taking precedence with embroider than with classic.
Is there any way to control the order that I'm missing?
The text was updated successfully, but these errors were encountered: