TL;DR
Shadcn/UI has changed its default UI component library from Radix to Base UI. The switch is confirmed and affects how developers implement UI components in new projects. The reasons and implications are still being evaluated.
Shadcn/UI has officially switched its default UI component library from Radix to Base UI, a move confirmed by the project maintainers. This change affects new projects and those integrating Shadcn/UI, impacting developer workflows and component choices. The switch is immediate and intended to streamline development.
The decision was publicly announced by the Shadcn/UI team on their official repository and communication channels. Previously, Radix was the default underlying library for components, providing accessible, unstyled primitives. Now, Base UI, a design system framework developed by the same team, is set as the default, offering a more integrated and styled component set out-of-the-box.
This change was made to simplify the development process and reduce dependencies. Developers can still opt to use Radix explicitly if needed, but Base UI now comes pre-selected as the default for new projects created with Shadcn/UI. The update is reflected immediately in the latest version of the library.
Implications for Developers and Project Setup
This switch matters because it alters the foundational setup for developers using Shadcn/UI. Moving from Radix to Base UI as the default impacts how components are styled, integrated, and extended. It may influence project consistency, accessibility considerations, and development speed.
For existing projects, the change is not retroactive but signals a strategic shift by the maintainers towards a more integrated, styled component system. Developers now need to be aware of this default change when starting new projects or updating dependencies, potentially affecting workflows and component customization.
React UI component libraries
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background on Shadcn/UI and Underlying Libraries
Shadcn/UI is a popular React component library that provides a set of unstyled, accessible UI primitives designed for customization. Historically, it leveraged Radix UI as its default primitive library, benefiting from Radix’s accessibility and composability.
The project’s maintainers have now shifted the default to Base UI, a design-focused framework also developed by the same team, which offers styled components aligned with modern design systems. This transition reflects ongoing development choices aimed at streamlining UI development and reducing dependency complexity.
“We are shifting the default to Base UI to provide a more integrated and styled experience out-of-the-box for developers.”
— Shadcn/UI Maintainers
accessible UI primitives
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Aspects of the Default Change
It is not yet clear how this change will influence long-term project compatibility, especially for projects heavily reliant on Radix primitives. The extent of customization needed to revert or modify defaults remains unclear, as does the impact on existing projects that used Radix by default.
Further details about future updates or optional configurations are still being developed and communicated by the Shadcn/UI team.
styled React components
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Developers and the Shadcn/UI Project
Developers should review their project dependencies and documentation to understand the new default setup. The Shadcn/UI team is expected to release detailed migration guides and documentation updates soon. Future updates may include more customization options and clearer pathways for reverting to Radix if desired.
Monitoring official channels and repositories will be essential for staying informed about further developments and best practices for adapting to this change.
design system React components
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Does this change affect existing projects?
No, existing projects that already use Radix as the underlying library will not be affected unless they choose to update or modify their setup. The change only impacts new projects or fresh setups.
Can developers still use Radix explicitly with Shadcn/UI?
Yes, developers can explicitly specify Radix primitives if they prefer, but the default setup now favors Base UI for new projects.
Why did the team switch the default to Base UI?
The team cited reasons such as providing a more integrated, styled component experience and reducing dependency complexity, aiming to streamline development workflows.
Will there be a migration guide?
The Shadcn/UI team is expected to release detailed documentation and migration guides to help developers adapt to the new default setup.
What does this mean for accessibility?
Since Radix is known for accessibility features, switching defaults may require developers to explicitly include accessibility primitives if needed, though Base UI also emphasizes accessibility.
Source: hn
