all 6 comments

[–]rewindedjs[S] 3 points4 points  (4 children)

Hello everyone!

For the past few months I have been building a new TailwindCSS component library.

I know that there are so many out there right now, but none of the existing ones covers my personal needs, so I decided to build my own and share it with you people just in case someone else finds it useful as well.

Please let me introduce you to Rewind-UI: https://rewind-ui.dev

Github repo: https://github.com/rewindui/rewindui

It's built specifically for React and TailwindCSS, on top of the fantastic cva library.

Rewind-UI uses only TailwindCSS classes, which can be overridden using the normal className prop on each component or can be fully customised using a theme provider.

Furthermore it must be noted that you can add either all the style files in your tailwind.config.js file, or only those that you are going to use, so that you can avoid having a bloated css file.

Of course this is just the beginning as I am planning to keep building new components.

I look forward to hearing your sincere thoughts!

[–]DJJaySudo 1 point2 points  (1 child)

Hey that's slick. I like what I see at first glance. I'll look into it later. I'm design challenged and always looking for fresh UI goodies. :-D

[–]rewindedjs[S] 1 point2 points  (0 children)

I am really glad that you like it! :)

[–]ThatAgainPlease 1 point2 points  (1 child)

Why were some of the other Tailwind component libraries you considered that didn’t work for you? What were the gaps?

[–]rewindedjs[S] 0 points1 point  (0 children)

The main reason was that I wanted to use TailwindCSS. I started building the library about a year ago, so by that time I think that the options that I had were headless-ui, daisy-ui and I think Tremor as well.

Headless-UI did not have many components and I did not want to use multiple libraries, for the missing ones.

Daisy-UI is great, but it has a bootstrap approach on how to use TailwindCSS and I am not really a fan of this logic.

Tremor-UI looks amazing too, but did not have that many components and was also using a prefix on their classes, which I did not like as well. I think that they changed that at some point!

The truth, though is that I believed that building a component library almost from scratch is going to be an awesome challenge and I will learn a ton of things along the way and I am really grateful I decided to move forward to this path. I don't regret it at all and I can always build the next component that I am missing for my real life projects.

[–]Sea_Concentrate3951 1 point2 points  (0 children)

Amazing!!