Piotr Monwid-Olechnowicz

> After making the change, I got a new error: Awesome! That confirms my suspicion. We need to transpile all JSX in the plugin to make it work as a...

@appsolut-jahn, @t2ca, could you try updating to `v0.14.5` and let me know if it fixes the problem on your side?

@nicfitzgerald Could you include the full error message?

If I were you, I'd probably use Theme UI _with_ Headless UI. They don't conflict. Theme UI is responsible for styling, Headless UI gives you some nice unstyled logic-only components....

So the idea is that Theme UI is only for styling, and Headless UI, Radix or Reach UI are only for logic. This way you can mix and match to...

> By the way, I am so stupid, that I cannot deal with Redix's component well. Yes they looks will, but have question under my global setting... If you have...

> OK, sorry... There's nothing to be sorry for, @PeterlitsZo. I just proposed I can help you out live on Discord if you have problems with Theme UI 😅

Hi @thecrowkeep 👋 Thank you for the issue! Very legit feature request! We've actually discussed it recently in https://github.com/system-ui/theme-ui/discussions/2264.

I had been initially conflicted about handling `sx` prop set to `undefined` differently than missing `sx` prop. However, I understand this remount can cause component state to be discarded resulting...

I'm working on a PR that will expose `Property.ZIndex` from Theme UI with the knowledge of your theme (so `"dialog"` will be autocompleted). My first attempts led to a really...