onyxia-ui VS tss-react

My advice if you don't have a multi-million budget and you only need to support React is to start from MUI components. Components like Date pickers, or Autocomplete are complex and time consuming to code from scratch. First thing you want to do is to build a custom theme for MUI (example DSFR, Example OnyxiaUI) this will make the MUI components roughly match your design system out of the box. Then you can create your own components that are wrapper around MUI components and customize them until they match your design (Example). Trust me, we always underestimate the complexity of building base component from scratch. There are tons of things to consider, I don't even mention the accessibility concerns... Customizing MUI components is the quick win route.

Shameless plug of our design toolkit: onyxia-ui. But it's good!

We are working on a UI toolkit that let you define what is the expected screen size. If you put 1920 for example and the screen is bigger than that it will stretch everything up. If the screen is smaller it shrinks everything down. It's not a perfect solution but it garanties that your app will look exactly the same no matter the screen size of your users. You can check it out here

Actually we are working on an alternative typescript first ui toolkit. tss-react is part of it. You can check it out it's onyxia-ui it rocks. It's still under active development but it's usable already. Also what's cool about it is that our salary are paid by the French tax payer so it's MIT, no strings attached.

What I meant is that the lib provides the tooling to do CSS-in-JS if you so choose. But it's not at all mandatory. There is a fully type safe class system you can rely on. Internally no CSS-in-JS is used. I personally do love CSS-in-JS (I'm the author of TSS) but I understand the case against it.

I'm not big on splitting things in neat little modules. Before we had logic.js structure.htm, styles.css then React suggested that logic and structure should be in the same file, it was the right move. Styles, in my oppignion, should be done in JS as well as well. I think that queries shouldn't be mangled with the UI stuffs.

Real-life examples: 1, 2, 3

Material UI v5 brought some amazing updates, but switching from JSS to Emotion had an arguably nasty side-effect: it was no longer as straightforward to group your component styles in classes. Fortunately, a fantastic library emerged that allowed developers to not only reduce the extreme pain from migrating all their classes from v4's makeStyles to emotion, but to also to continue to writing classes in practically the same syntax, with wonderful TS type-safety. This library was tss-react, and it was one of my favorite open source discoveries of 2021.

You can still use makeStyles with tss-react, as documented here: https://mui.com/guides/migration-v4/#2-use-tss-react. I've used it and it seemed to work quite well.

tss-react