I'd like to use NuxtUI in an application where we hope to use StyleX instead of Tailwind.
While, sure, we could install both, compile two css files that end up loaded both... That's not going to be as efficient (both for build and runtime) as a single StyleX or single Tailwind file.
One could use Headless UI directly... but Nuxt UI also provides a few more goodies, which would be nice to keep, while we style the components using StyleX. Possibly with custom styles for everything if we have to.
Of course, having first class StyleX support would be even better, but I understand that may be too much of undue maintenance burden. Having a base that has all the functionality, but no built in styles and icons, in order to be fully customizable (including by the full version itself...) is the next best thing.
Description
I'd like to use NuxtUI in an application where we hope to use StyleX instead of Tailwind.
While, sure, we could install both, compile two css files that end up loaded both... That's not going to be as efficient (both for build and runtime) as a single StyleX or single Tailwind file.
One could use Headless UI directly... but Nuxt UI also provides a few more goodies, which would be nice to keep, while we style the components using StyleX. Possibly with custom styles for everything if we have to.
So from the list of features, that means
Of course, having first class StyleX support would be even better, but I understand that may be too much of undue maintenance burden. Having a base that has all the functionality, but no built in styles and icons, in order to be fully customizable (including by the full version itself...) is the next best thing.
@nuxt/ui-core
I guess you can call it.Additional context
No response