Watch this if you use shadcn/ui
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
This is bad...
Theo - t3․gg
104.3k views
I wish this was clickbait
Theo - t3․gg
103.1k views
Are you f**king kidding?
Theo - t3․gg
201.9k views
Where Should You Deploy In 2026?
Theo - t3․gg
102.6k views
if you’re overwhelmed by AI tools, watch this
Jeff Su
34.2k views
I was wrong
Theo - t3․gg
69.3k views
You're falling behind. It's time to catch up.
Theo - t3․gg
132.6k views
You're logging wrong
Theo - t3․gg
59.7k views
You're in a simulation, please watch this
Moon
62.0k views
Shadcn just changed forever
Theo - t3․gg
112.2k views
Top Comments (10)
js dev's can't like something for more than 6 months huh
Finally a video not about AI. I do enjoy AI related content but it's good to have a break sometimes lol
> Copy your whole `ui/` > Copy the whole Base docs > Throw it into LLM (Gemini 2.5 Pro works perfectly for me) > Ask it to remap Radix to Base Profit
I’m legally blind, and even with my very small side project I’m experiencing weird accessibility issues with ShadCN/Radix. Which is especially frustrating since I went with it precisely because it was supposed to be good at accessibility.
shadcn code may live in your repo, but let's be honest, it mostly re-exports other libraries with some tailwind classes applied. The underlying primitives do not live in your codebase and their implementation is way more complex than you might expect. The problem is there is enough internal integration/dependency between components within a given ecosystem (and not nearly enough escape hatches) to make mixing painful, if at all feasible. More often than not you'll run into major problems if you don't go all-in, especially with `react-aria` or `radix`.
love how every time some drama is about UI, seems like everyone is reasonable and just has a nice conversation appreciate you covering this, was way out of proportion in my head
That radix bug finally explains why I was getting this infinite error bug in my code that I simply couldn’t explain
Tanstack UI will save us all. When Tanner decides to make it
17:52 That Shadcn take was on point!! Absolutely agree! I love being able to actually fix stuff for my use cases MYSELF whenever rarely needed.
I’m on several projects at the moment and I think I prefer the bootstrap approach in the end… I can abstract their components if needed to bespoke ones for the app at hand, augment it with normal CSS if needed and it’s easy to hook into behaviour and attach dom events if needed (sometimes tricky with Radix based libs)
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
js dev's can't like something for more than 6 months huh
Finally a video not about AI. I do enjoy AI related content but it's good to have a break sometimes lol
> Copy your whole `ui/` > Copy the whole Base docs > Throw it into LLM (Gemini 2.5 Pro works perfectly for me) > Ask it to remap Radix to Base Profit
I’m legally blind, and even with my very small side project I’m experiencing weird accessibility issues with ShadCN/Radix. Which is especially frustrating since I went with it precisely because it was supposed to be good at accessibility.
shadcn code may live in your repo, but let's be honest, it mostly re-exports other libraries with some tailwind classes applied. The underlying primitives do not live in your codebase and their implementation is way more complex than you might expect. The problem is there is enough internal integration/dependency between components within a given ecosystem (and not nearly enough escape hatches) to make mixing painful, if at all feasible. More often than not you'll run into major problems if you don't go all-in, especially with `react-aria` or `radix`.
love how every time some drama is about UI, seems like everyone is reasonable and just has a nice conversation appreciate you covering this, was way out of proportion in my head
That radix bug finally explains why I was getting this infinite error bug in my code that I simply couldn’t explain
Tanstack UI will save us all. When Tanner decides to make it
17:52 That Shadcn take was on point!! Absolutely agree! I love being able to actually fix stuff for my use cases MYSELF whenever rarely needed.
I’m on several projects at the moment and I think I prefer the bootstrap approach in the end… I can abstract their components if needed to bespoke ones for the app at hand, augment it with normal CSS if needed and it’s easy to hook into behaviour and attach dom events if needed (sometimes tricky with Radix based libs)