Unfortunately, I'm going to have to dunk on the irony of developing a CSS-first toolkit then only releasing headless React components. At least if you used Svelte or WebComponents directly you could compile them down to bind to other frameworks.
I'm not a React hater, but it's time for React-only support for UI toolkits to end. There are other compelling frameworks that are also worth using that are better choices in many cases.
I’m disappointed they went with React as well. There are definitely more innovative frameworks (my favorites: Vue and Svelte).
But I do understand the Tailwind team - it is an economic decision. React (still) dominates.
Going framework-agnostic is (currently) not a good approach imo. The developer experience would suffer too much. I hope in the future agnostic UI kits become a thing, but the tooling around this approach needs to change first.
I'm not a React hater, but it's time for React-only support for UI toolkits to end. There are other compelling frameworks that are also worth using that are better choices in many cases.