Shadcn/UI now defaults to Base UI instead of Radix

Join the discussion

• Hacker News
• based
  by skeptrune
• Imagine building a brand new component library to replace your already quite successful component library and still making it React-only.
  by TheFuzzball
• This reads like a script to a Theo video
  by geophph
• Most of the websites I found are still on the radix version.
  by ruguo
• Tangential but does anyone an have opinion on Base UI vs React Aria?

  Trying to decide between the two atm.

  by kcrwfrd_
• Personally I'd prefer React Aria; I don't have the patience to try understand why suddenly everyone is rushing to adopt Base UI instead of Radix which itself was once suddenly the thing everyone rushed to instead of Stitches.

  Having a library not in anyway related to that to me feels like a big pro.

  I have found React Aria to be very good. I really like how its a set of hooks, a set of premade components using said hooks, and I like how you can choose bits of either approach for your own components. Some of the hooks are very useful.

  by lloydatkinson
• I'm still on Daisyui and feeling FOMO here. Is it worth the switch and why?
  by xiaoape
• Curious if anyone tried Astryx that was open sourced by Meta last week to see how it compares.
  by vjeux
• Why? What advantage does it bring?
  by nullbio
• Yeah instead of this slop a simple table explaining the tradeoff would have been far superior.
  by stefan_
• Base UI is more low-level, a lot less opinionated and doesn’t force you into certain layouts. This of course makes it more complex to use, but that doesn’t matter if you’re using shadcn components because they’re doing that work for you.

  So essentially they look and operate the same as Radix components at the shadcn level but you have low-level control later on should you need it.

  by dabinat
• url should be https://ui.shadcn.com/docs/changelog/2026-07-base-ui-default
  by nektro
• Shadcn is great until you want to use it
  by pgisapedo
• Why ?
  by goldenarm
• That'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.

  [0] https://www.9ui.dev

  by Topfi
• What's the difference?

  All of these component libraries look the same.

  by nullbio
• My choice is https://www.skeleton.dev/
  by vmware508
• Why? There's a thousand component libraries, what makes this one stand out?
  by esperent
• I want to use shad-CN but instead end up defaulting to Mantine everytime. Its just so much faster than having to remember which contexts to wire in.
  by another_twist
• I miss a good old skeuomorphic styleguide. I guess the last one was Blueprint?
  by klaussilveira
• Would that lead to anything better for the users, such as a smaller bundle size? Or is it more of a QoL change for Shadcn maintainers?
  by ahmedehab_01
• On React Native support: https://github.com/mui/base-ui/issues/2612
  by rplnt
• What is the shadcn/ui equivalent for Angular?

  PrimeNG had a licensing change recently and I'm looking at a suitable alternatives for a fresh project.

  by 8cvor6j844qw_d6
• https://www.zardui.com
  by microflash
• I'm in the same boat. We've been using PrimeNG for several apps at my job, and until we find a suitable replacement, we'll be stuck on using Angular 21.

  That being said, a group did fork PrimeNG, and plan on maintaining it (new name pending)

  https://github.com/openng-org/open-prime

  by sphars
• https://spartan.ng/
  by mhfu
• I'm building Lily Design System as a response to Shadcn and similar systems not yet being available directly for multiple stacks including Svelte, Angular, Nunchucks. It's all free open source. If you want to send me your feedback, suggestions, etc. I can easily add things to Lily.

  https://lilydesignsystem.github.io

  by jph
• > PrimeNG had a licensing change recently

  Both attempts [1] to surface this on HN failed but if you are using a PrimeTek component library you need to be aware of this change.

  PrimeNG, PrimeReact, and PrimeVue are all going fully closed source and ongoing licencing will be $800 per developer seat in 2027. [2]

  The previous repos have been archived. [3]

  PrimeFaces remains open source but it's now developed and maintained by independent volunteer developers who are not employees of PrimeTek.

  [1]: https://hn.algolia.com/?q=The+Next+Chapter+of+PrimeTek

  [2]: https://primeui.dev/nextchapter

  [3]: https://github.com/primefaces/primeng

  by cube00
• Moving 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.

  by dyllon
• 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.
  by kristiandupont