Shadcn/UI now defaults to Base UI instead of Radix
ui.shadcn.com
Shadcn/UI now defaults to Base UI instead of Radix
1–10 of 180 posts
Re: Shadcn/UI now defaults to Base UI instead of Radix
#2[deleted]
Re: Shadcn/UI now defaults to Base UI instead of Radix
#3That's great. Started using Base UI early on via 9ui [0] and found the primitives very pleasant to work with, especially if one wants to compose more complex components from other Base UI components. Maybe Shad can reduce some of the dependencies they rely on now.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#4Moving away from codemods and towards LLMs doing migration work is an interesting development.
Even if they’re more deterministic, I wonder if the days of codemods are numbered.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#5Moving away from codemods and towards LLMs doing migration work is an interesting development. Even if they’re more deterministic, I wonder if the days of codemods are numbered.
I think the two complement each other perfectly and will continue to do so. I keep writing AGENTS.md files for soft rules and custom linter rules for hard ones which IMO is the best of both worlds.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#6[flagged]
Re: Shadcn/UI now defaults to Base UI instead of Radix
#7I have used and mostly like Shadcn, and yet their Radix-based radio button was a bit much, as are other choices, where similarly overblown solutions were used.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#8For boring applications - do people prefer the copy paste approach of shadcn instead of a traditional ui library like mantine?
The copy paste approach may be easily modifiable but creates new problems - ie now there is an upgrade ai agent for something that should just be ticking up a version number.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#9based
Re: Shadcn/UI now defaults to Base UI instead of Radix
#10For boring applications - do people prefer the copy paste approach of shadcn instead of a traditional ui library like mantine? The copy paste approach may be easily modifiable but creates new problems - ie now there is an upgrade ai agent for something that should just be ticking up a version number.
Martine just straight up sucks.
Vendoring your components gives you the best of both worlds. You get a full component library but retain the ability to modify them as you want.
Your AI agent claim doesn't make any sense either. When upgrading normally your component just gets rewritten on disk. When switching from radix to base ui, a more comprehensive approach is needed.