tailwind ui library or do I build myself?
Coming from svelte, I love using Tailwind, and honestly, I'd like to keep it that way. Now - I'd like to work on a project in react (probably t3/next, idk) but idk which ui library to choose. Do I build my own? Do I use, idk, DaisyUI, so something unrelated to react? imo the list of tailwind react libraries is quite lacking compared to my expectations. There's NextUI, shad (which i don't like cuz I don't wanna store their component :p), aaaaaaaand.. thats it for react specific ones I think? idek
8 Replies
honestly I think I'd be down to give shad a honest attempt if it were bundled like any normal ui library-
aldoe it is a bit too monotone for me, idk
honeslty chakra looks promising imo. but im not a fan of mixing non-tw and tw
If you want to modify the components' styles or behavior, I'd recommend shadcn. If not, either one is good
Shadcn is basically helping you create your own component library. That's the point. That's why you need to commit them
ah, fair. I'm not sure if I like that tbh, but I'll consider it
shadcn is probably the best option atm
which i don't like cuz I don't wanna store their componentno one says you have to touch them 🤷 they're pretty good out of the box
I've heard great things about https://mantine.dev/. I don't think it's built from tailwind like shadcn/daisyui but it should play nice with tailwind unlike MUI (you might have to disable preflight though). Other options include Headless UI, Flowbite, Kitwind, MerakiUI, TW Elements, HyperUI, TailwindFlex
mantine just doesnt make sense
idk wtf the people behind it thought
using context making it all have to be within use client components
iirc chakra got the same issue :LUL:
oof, that's a big L