This comment is in conflict with your first comment. You first pointed out that to achieve the true obfuscation of CSS selectors one needs to use that lib which does renaming. Now you state that you use CSS modules, which is legit. As I stated in the article, if you are not comfortable with 4 character long obfuscation just go with 5 or 6 or … also, Webpack can be configured to add prefix _ if conflict occur. Which we did implemented. So our classes are obfuscated into 4 char long strings at best and at worst they are 5 chars long.
That library is nice for production but I have no clue why you state that you don’t have third party CSS which can break the system. In the article it is not described that one should go with such approach. This is all about CSS modules, React and Webpack. Where you write your CSS or SCSS in a way it does not include any weird non standard stuff.
Additionally in dev environment we don’t have any CSS selectors renaming. Which is the most secure way to make sure that your CSS is written in the error prone way. One needs to name the classes in a way which secures the encapsulation on the level of methodology. That is why BEM exist.
Thanks for the comment. It is opinionated topic and we are more than less talking about the same thing.