This is probably not a very good general recommendation, but inline CSS actually makes quite a bit of sense to me when using React&#x2F;Redux.<p>Style is generally heavily interconnected with app state in modern web apps, so why not take advantage of a sophisticated state management system like Redux to declaratively manage your styles along with your state rather than adding&#x2F;removing class names at runtime imperatively? With React&#x27;s implementation of inline-styles, you can treat your styles as just another piece of JS data in your state tree, and have the entire power of the JS language at your fingertips to compose&#x2F;extend&#x2F;manage them, including powerful functional transformations, a flexible and statically analyzable module system, and prototypical inheritance, if you&#x27;re into that kind of thing.<p>With this approach, you completely remove any need for preprocessors, get rid of a whole class of CSS limitations like the lack of a proper module system, and global scoping and the associated specificity issues, and your components become truly self-contained by default.<p>That said, I don&#x27;t have a lot of actual experience with this approach in practice, so I definitely could be missing some nuances and practical limitations. I&#x27;d love to hear some opinions&#x2F;experiences regarding using inline styles in React&#x2F;Redux.