shadcn/ui is great! But what if...

[@GatoNordico]

I think it depends on who’s the intended user. I would say shadcn is a great starting point for someone who wants to have the flexibility to modify their ui components. And as you highlighted this flexibility comes with a cost, which in this case is not monetary…

[@rchuhk100]

Very helpful video! Thank you.

[@hubcio2115]

The aforementioned arguments are valid, but imo they're just small caveats. One point about big codebases is a good thing to consider but shadcn is still better then a component library. What you trade off with shad you'll pay when fighting against a library or hacking it to do something that it was not designed to do.

[@DevLeonardo]

Yeah, I agree with that. There are some tradeoff like everything but so far it seems they're better than the ones with other libraries/approaches.

[@austincodes]

It sucks when a library takes you 90% of the way there to your solution. Then the last 10% is hell because you have to hack it into doing something it wasn't designed for. Breaking changes and updates are also a pain. I'd so much rather own my code

[@bnssoftware3292]

​@@austincodesTHIS! This is almost ALWAYS the case with third party libraries, paid or not. Always look great in the provided examples, but always fall short when actually trying to use them.

[@sourabhsingh4515]

the developer of shadcn must be his classmate that's why he is just telling us what we already know and we don't care about those things 🤣🤣

[@austincodes]

If there is a problem with shadcn you can make a pull request. If you are using MUI are forced to fix a bunch of random breaking changes because you wanted a newer version for a single component or bug fix. MUI and things it are terrible

[@sid06]

Thanks for mentioning this, it has been very valuable for making my decision (I will stick with JoyUI).

[@MrPkmonster]

Hello, could your suggest alternative library instead of shadcn ? Thank you

[@xxxxxxxxxxxxxxxxxxxxxxxxx981]

nextui is good and it's an actual library. it has a premium side, but it's optional

[@SirJagerYT]

DaisyUI

[@angstrom1058]

"Dependency Hell" Thanks for pointing this out.

[@trangcongthanh]

0:42 The ownership of the code is the best feature of shadcn/ui. I rather try to resolve the problem by myself than create issue, wait author/contributor verify the issue, fix it, then release it. I even created the PR to fix the bug, but it never got merge. Or got merge but never released. In the end of the day, I need to maintain a fork of the library by myself. Is it less work compare to maintain shadcn/ui components? 2:48 You can config the tsserver to ignore some pattern from auto/suggest import ("typescript.preferences.autoImportFileExcludePatterns": []) Yes, upgrade deps for long run project is always a pain.

[@smithrockford-dv1nb]

The problem is that all other libraries (MUI, next-ui, etc) all look bad by comparison. Vercel has mastered the look, and shadcn/ui is the only one that looks close.

[@salamandr4111]

nextui looks great imo

[@cb73]

There are downsides but… compared to what?

[@nasko235679]

A lot of the components (or primitives whatever) also don't work together. Let's say you want to insert a DropdownMenu inside a NavigationMenu. Everything spazzes out and the component starts getting rerendered constantly. Yeah, it can be annoying and time-consuming to write your own components but after spending days trying to stitch up a dropdown multi-nested navigation from shadCN components and failing, I'd say I would've been better off doing it from scratch.

[@emmanuelxs6143]

I think we can come up with a solution

[@wadoudazer6906]

What about solution , i hate the way chakra material and mantine works with classic css or css in js (emotion) i really like tailwind

[@jamiuadeleye]

Tailwind also works well with mantine.

[@hakuna_matata_hakuna]

am now afraid of updaing the depndancies because all the radix ones wil update and something will bvreak . parkui better imo snec they only use ark ui which they also maintain , it also workswith solid ans sveltte

[@anthonydattolo6297]

Can’t use it on react native

[@isenewotheophilus6485]

My take on your video: It's BS

[@s_the_first]

"if your component has a problem, it is... YOUR problem". Lol. You are correct. But this is a good thing. Funny tho...