Deterministic ordering for CSS modules when order otherwise conflicts

[Knagis]

In our repo we currently have a LOT of warnings

Conflicting order between css ./file1.css and css ./file2.css

We suppress these warnings since we do use CSS modules and very rarely pass the classnames between components..

However, we do that sometimes, it actually triggered a bug when we changed from mini-css-extract-plugin to builtin css support and the order changed.

Thus a question - is it possible via some compiler hook or could it be added as a builtin config flag - to have specific deterministic order, that ignores the import order and instead orders the output by, for example, filename. Split chunks changing could still end up with non-deterministic output, but it should be way less likely.

[alexander-akait]

Can you take a look at this - #20978, is it fit for you?

[Knagis]

Yes, seems perfect for my situation.