tss-react VS compodio

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

Components that need to incorporating global styles like colour schemes, breakpoints, border radius, scss mixins is where I've found it tricky to fully decouple. In these instances I've resorted to using global custom properties that I can reference inside css modules and importing commonly used scss mixins. This is an example of a search box component incorporating global things.

Currently working on compodio in my free time. A website that makes it easier to find, and subscribe to community radio shows as a podcast. It uses NextJS, Python, PHP, MySQL

I used it here in a function that constructs a string of hex colours for a css gradient from an array. I spend more time in python than JS, and looking at this code again now I see it certainly isn't perfect.

I feel like now that I'm developing mostly with react, which has everyone rethinking how to think about separation of concerns, I'm still figuring things out again. In a current project, I have global styles sheets for the site as a whole, then I try to bundle css modules for components of a site in a folder with other files related to the component (ex. a main menu component). The aspiration being that some components will be generic enough that I could just copy one folder and have everything I need (css, js, etc) to add that feature to another project.

Impressive. I've been working on something similar, but much simpler. I settled for just organizing colours by lightness. I just might borrow your ant colony optimization.

This is an in progress component I'm working on that always expects to receive an array of available image sizes, that jpg/webp are always available.

Then You can pretty much do the same thing I did with the next page link here.