base style + DB fetched styles + runtime styles. Good use case for jess?

[lveillard]

but it can produce "patch-able" CSS, along with a module that can patch your CSS at any time. It's kinda magic.

Hello, I just read that sentence in your docs and looks promising.

We have a pretty weird use case where we serve in a single nextjs app multiple different stylesheets, like each user might have some specific styling for the components stored in DB

The 3 solutions we are exploring:

• Runtime (we tried twind and unoCss's runtime version) => This is easy but generates FOUC. Or a long loading time. Being able to do the runtime logic in the server side would help, but then any dynamic styling over that already dynamically db-fetched style would be not possible.
• Compile somehow each styleSheet from each user and add it somehow 😅
• Limit the customization to tailwind classess and safelist everyclass.

Reading throw your docs it seems like this lib does what I'm dreaming of, an hybrid. Being able to pre-compile the default style but patch it with db.fetched styles or with client-side js style impacting runtime logic.

So my questions is: do you think Jess migh fit this weird use case? Thanks!