- 🇬🇧United Kingdom catch
Everything in the issue summary has been done now, except for:
Intelligently sort CSS and JS files so that we don't break aggregation groups
This currently happens when CSS or JS that can not be preprocessed (because it is external, inline or conditional) is added in the middle of a group. Possible solution: Move such CSS / JS to the end of their group so that they end up in between 2 aggregates instead of splitting an aggregation group. This slightly changes the order of the CSS / JS output which, in some cases, affects CSS overrides, but with proper documentation that shouldn't be a problem (themers can just use more or less specific CSS rules).However I don't think we can do that - for example ckeditor5 explicitly relies on this behaviour.
We have other aggregation issues still open that aren't in the issue summary, but closing this one as outdated.