Non Tailwind version?

[Daniel15]

Would you ever consider releasing a version of this library that doesn't depend on Tailwind, using Astro's native scoped CSS support instead?

I'd like to use the components on some projects but I don't really want to pull in Tailwind just for them (since I'm not using Tailwind otherwise). Tailwind classes also make it a bit of a mess to override things, like to change the padding or margin.

[thomkrupa]

Hey @Daniel15, definitely not rejecting the idea, it's something we'd like to explore.

We already do plenty of class/component transformations in our pipeline, and our components carry semantic data-* attributes (data-slot, data-variant, etc.), so a scoped-CSS version should be doable.

Let me experiment a bit before I put it on the roadmap. Will report back!

[vitalijalbu]

Would you ever consider releasing a version of this library that doesn't depend on Tailwind, using Astro's native scoped CSS support instead?

I'd like to use the components on some projects but I don't really want to pull in Tailwind just for them (since I'm not using Tailwind otherwise). Tailwind classes also make it a bit of a mess to override things, like to change the padding or margin.

look at those, if you want tailwind:
https://ui.full.dev/
https://basecoatui.com/
https://starwind.dev/