Support for reka-ui

[Xen0Xys]

Hello, Does ui-things support shadcn 1.0 and new reka-ui (radix-vue 2.0) ? Thanks for your amazing job ! 😄

[BayBreezy]

Hey @Xen0Xys , I am not sure i understand what you mean by "support shadcn 1.0" I tried reka-ui and it is great so far. I plan on upgrading to reka-ui and tw4 in the coming months. since everything is so new right now, I am waiting to see how things progress.

I am not sure how the upgrade will go. I think I will have to create a different version of the ui-thing website and cli.

[Xen0Xys]

Thanks for your answer! Nevermind I was thinking that ui-things was based on shadcn components 😅 So, I will keep a look on how things will go!

[BayBreezy]

I mean, the components are similar. I just did not do the whole new-york style thing. I also added a few other components outside of what is documented in shadcn

[BlueBazze]

I did a global search for radix-vue and replaced it with reka-ui There are a few tweaks here and there, but its a pretty smooth transition. Along with replacing morev transitions with motion vue.

[BayBreezy]

Nice. I did test it out myself and it was great indeed. I did not make the change from morev to motion-v tho.

I also tried TW4 and a lot of stuff broke lolol the sidebar was hard to update but I got it working.

The biggest challenge for the tw4 & reka-ui upgrade is gonna be re-writing the CLI. I will make the jump when I have time to fix all the issues that will come up immediately after upgrading.

I was also considering just doing a v2 of the entire thing. That way, the ppl who can't upgrade just yet can still use the v1(this current version). Thoughts?

[Xen0Xys]

I think that releasing a v2 could be great (it seems that shadcn-vue did that). Can't wait to see the release :)

[BayBreezy]

Yea.

Looking at what is over at shadcn-vue now, I am definitely gonna wait a bit. shadcn-vue will have to make another major change soon for TW4(I predict).

The move from the tw.config file to pure css is not a small one and a lot of the component classes will have to change.

[Xen0Xys]

I can't wait to see the release, but yes take your time to make things right, it will be better for everyone.

[BlueBazze]

Biggest problem with tw4 is getting it to actually work. Tried it and messed up.

Have been eyeing unocss for a while, but now with tw4 i dont know anymore.

V2 seems fine.

[BayBreezy]

Hey all 👋🏽,

I think it is time to start making the move to Reka UI + TW4. I know some things will have to change. Like upgrading to tw-animate-css and moving out the different transitions from morev to something like motion-vue.

I will also need to update the cli. I am thinking of doing a re-write. I want to make it closer to what is happening over at shadcn-vue. so maybe use that little json file to configure stuff.

Thoughts?

• [x] Update to Reka UI
• [x] Update to TW4
• [x] Re-write CLI
• [x] Update components to match new TW class syntax
• [x] Remove toast in favor of sonner
• [x] Use new-york theme. shadcn-ui and shadcn-vue is using it so why not 🤷🏽‍♂️ (This will be a big change. If anyone objects, please share why)

Did I miss anything?

[alikavoosi1001]

Hi. yet you haven't able to upgrade to Tailwind 4? I thank you a lot for the of ui-thing. But unfortunately there are a few days that I have been in trouble because of the TailWind project upgrade and I can't use your components.

[arshx86]

Hey all 👋🏽,

I think it is time to start making the move to Reka UI + TW4. I know some things will have to change. Like upgrading to tw-animate-css and moving out the different transitions from morev to something like motion-vue.

I will also need to update the cli. I am thinking of doing a re-write. I want to make it closer to what is happening over at shadcn-vue. so maybe use that little json file to configure stuff.

Thoughts?

• [ ] Update to Reka UI[ ] Update to TW4[ ] Re-write CLI[ ] Update components to match new TW class syntax

Did I miss anything?

Hey, thanks for updates. Those seems enough to catch-up shadcn-vue.

and also;

1. Deprecate toast for vueSonner like they did in original shadcn.
2. OG shadcn has deprecated default theme with new york we can do same (I also think new-york suits well for shadcn :D)

[BayBreezy]

Hi. yet you haven't able to upgrade to Tailwind 4? I thank you a lot for the of ui-thing. But unfortunately there are a few days that I have been in trouble because of the TailWind project upgrade and I can't use your components.

It's gonna be upgraded in the coming days 🙂

[BayBreezy]

Hey all 👋🏽, I think it is time to start making the move to Reka UI + TW4. I know some things will have to change. Like upgrading to tw-animate-css and moving out the different transitions from morev to something like motion-vue. I will also need to update the cli. I am thinking of doing a re-write. I want to make it closer to what is happening over at shadcn-vue. so maybe use that little json file to configure stuff. Thoughts?

• [ ] Update to Reka UI[ ] Update to TW4[ ] Re-write CLI[ ] Update components to match new TW class syntax Did I miss anything?

Hey, thanks for updates. Those seems enough to catch-up shadcn-vue.

and also;

1. Deprecate toast for vueSonner like they did in original shadcn.
2. OG shadcn has deprecated default theme with new york we can do same (I also think new-york suits well for shadcn :D)

Thank you for sharing. I updated the list. The docs will be updated way before the CLI. That way ppl can copy and paste the components and have it working in their TW4 projects.

I wanted to stick with the tailwind module for nuxt but they are just implementing tw4 stuff and it is in beta at the moment.

I may have to exclude it from the CLI...

[BlueBazze]

The entire thing can more or less just be search and replace "radix-ui" -> "reka-ui" but there are some changes for props and changes in reka that is not immediately noticible.

tw4 isnt a hazard anymore, pretty straight forward. And wouldnt suprise me if theres an eslint plugin to find all the tw3->tw4 changes in the project. If you run into an issue where a component or multiple seems to have their tw classes but no actual css it is most likely because the tw vite plugin didnt recognise the source file so you'll have to mark it manuallly - https://tailwindcss.com/docs/functions-and-directives#source-directive Specifically layers in nuxt dont get recognised - @source "./layers/"; should fix it.

There are a few personal pit falls with reka. For instance the entire createContext thing is basically just a more cumbersome provide/inject for people who didnt bother reading the vue documentation. Which is the only problem i can think of at the moment, and is not really a problem.

The "hardest" issue you will face is tailwind and the deprecated utilities.

The biggest improvement i've found with Nuxt and shadcn is actually putting the Ui components in a Ui layer.

[BayBreezy]

@BlueBazze I wish it was that easy 🤣. The Radix -> Reka update is simple. Only a few components need an update. the tw3 -> tw4 update is painful!! Everything that could break, did break. I am going down the line of components and I am currently on the buttons page. As soon as a working version of the upgrade is available, I will publish it so everyone can take a look

[amerkay]

the tw3 -> tw4 update is painful!! Everything that could break, did break.

Hi. Great work. Your Blocks that you're giving away with an MIT license is saving me a lot of time!

I could not find the branch you are working on for the tw4 upgrade. If you share your progress on a dev branch, I can help look into it & with the tw4 upgrade.

[donPuerto]

I think we should move forward instead of waiting for @nuxtjs/tailwindcss. Nuxt UI is already using Tailwind CSS v4, so hopefully the UI Thing work can continue as well.

[BayBreezy]

Hello All, If you get the chance, check out this branch here: https://github.com/BayBreezy/ui-thing/tree/feat/update-to-rika-ui-and-tw4

The docs will need some updating but all components are now up to par with TW4, Reka UI is being used & motion replace morev transitions. Lemmi know if you see any issues or just do the fix if you have the time. Thanks in advance 🙏🏽

[BayBreezy]

And for those of us who are too lazy to pull down the code here: https://uithing.com

Please note: The Getting started section is completely out of sync. This part of the documentation will be recreated.

Also, the CLI has not been updated yet. I will update it soon. Nuxt 4 just got released yesterday. I am still not sure what is happening with the @nuxt/tailwind module but I had to drop it in order to get the update to work.

Please click around and let me know what breaks 😄

[donPuerto]

More power brother

[BayBreezy]

Hello everyone,

The CLI is somewhat working with Nuxt 4. It will be a major release with breaking changes(there was no way around that part sadly)

It can be found on this branch(if anyone wants to test it out locally): https://github.com/BayBreezy/ui-thing-cli/tree/v1-update

There is one issue thus far with the Calendar and Datepicker components. They both rely on the nuxt module that lives here: https://github.com/samk-dev/nuxt-vcalendar

I already opened a PR for it to be fixed: https://github.com/samk-dev/nuxt-vcalendar/pull/25

Hopefully it gets merged soon. If not merged in a month, I will have to create my own version of the module.

[BayBreezy]

Hey everyone 👋

Quick update: the calendar component issue has been fixed ✅.

Big shoutout to the community member who forked the library and patched the compatibility problem. I’ve merged their fix back in.

I think it’s safe to close this issue soon, maybe after a week of keeping an eye on it just in case. Thanks so much for your patience while this got sorted out, I really appreciate all of you checking out and using the library 🙏.

A couple of other notes:

I added templates for bug reports and feature requests, so hopefully those make contributing smoother.

The changelog is still hilariously out of date 😂 but I’ll catch it up as I go.

I’ve also started porting components from Magic UI into UI Thing — so keep an eye out for those!

Thanks again for being part of this little journey. 🚀

[therealokoro]

I'll be contributing some components in my free time, I love UiThing