Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
When you add the CSS-Modules to the mix with your React (or similar) project, you eliminate any need for other SASS/SCSS functionality. There are so many other benefits to the CSS-Modules pattern btw. My favorite is that it becomes much easier identify which elements are affected by a given CSS class. This is because you're importing and using your css module file like it's an object. Each property in that object is a class name from the css module file. Bonus if you're using TypeScript as your build will fail if you have typo in a class name. Note: CSS-Module compilers will generate a unique hash for css class names you declare in a CSS-Module so don't worry about coming up with unique class names across modules.
Another argument I should have made earlier is that, to my knowledge, Sass/SCSS isn't commonly tested. I found this library, true but have never used it personally. In any case putting logic into css would warrant testing it so now you need to add another test runner to your project. That's a huge factor to consider.