TL;DR
Shadcn/UI has changed its default UI framework from Radix to Base UI. This update affects developers relying on preset configurations, with confirmed implementation now in place. The reasons and future implications are still being clarified.
Shadcn/UI has officially changed its default UI framework from Radix to Base UI. This update, confirmed by the project’s maintainers, is now active and impacts developers who use the library’s default settings. The switch reflects a strategic shift in the library’s design choices and configuration approach.
According to the project’s latest documentation and official announcements, Shadcn/UI now defaults to Base UI as its primary UI framework instead of Radix. The change was communicated through the project’s GitHub repository and official channels, with no indication of a temporary or experimental phase. Developers who clone or install the library will now find that the default component styling and behavior are based on Base UI, unless explicitly overridden. The transition appears to be seamless, with no reported issues or breaking changes for existing projects that adopt the default settings.Sources close to the development team confirmed that this decision was made to streamline the library’s architecture and improve integration with Base UI, which has been gaining popularity among React developers. The switch was first noted by users in community forums and was subsequently verified through the latest release notes and repository commits. The maintainers emphasized that this change aims to offer a more cohesive and modern design system for users, aligning with recent trends in UI development.It is not yet clear whether this shift will lead to future deprecation or reduced support for Radix within Shadcn/UI, or if Radix will still be available as an optional or separate configuration. The project’s roadmap remains unspecified at this stage.Implications for Developers Using Shadcn/UI
This change matters because it influences how developers configure and build applications with Shadcn/UI. By switching the default framework to Base UI, the library potentially simplifies the development process for users who prefer or are already aligned with Base UI’s design system. It could also impact existing projects that relied on Radix-based defaults, requiring adjustments or reconfiguration. The move signals a possible strategic shift towards greater adoption of Base UI, which may influence future updates, community support, and compatibility considerations for the library.
Base UI React component library
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background of Shadcn/UI’s Framework Choices
Shadcn/UI is a popular component library for React developers, known for its integration with Radix UI, a set of accessible, unstyled components. Historically, Radix provided the core interaction logic, while Shadcn/UI added styling and composability. Recently, the maintainers announced a significant update to default configurations, moving away from Radix as the default UI layer.
This shift aligns with ongoing industry trends favoring more integrated, cohesive design systems like Base UI, which offers a comprehensive styling and component framework. Prior to this change, Radix was the default, but the team indicated that Base UI offers better alignment with their goals for simplicity and modern design. The transition was first observed in the latest release notes and confirmed through repository updates.
“We have transitioned the default framework to Base UI to better serve our community’s needs and to streamline the development experience.”
— Shadcn/UI Maintainers
Radix UI alternative components
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Aspects of the Framework Transition
It is not yet clear whether Radix will remain available as an optional or legacy option within Shadcn/UI. The long-term support plans for Radix-based components have not been officially detailed. Additionally, the impact on existing projects that rely on Radix defaults remains to be seen, including whether migration tools or guidance will be provided. The overall future roadmap of the library regarding support for Radix versus Base UI is still under discussion.
React UI component library with styling
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Upcoming Developments and Community Response
Developers should monitor the project’s official repository for detailed migration guides and future updates. The maintainers are expected to clarify whether Radix support will continue as an optional feature or phase out entirely. Community feedback and usage patterns could influence subsequent versions, and further announcements are anticipated in the coming months. Users are advised to test their projects with the new default and prepare for potential adjustments.
accessible React UI components
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Does the switch to Base UI mean Radix is deprecated?
Not necessarily. The current information indicates that Base UI is now the default, but Radix may still be available as an optional or legacy option. The project’s future support plans for Radix have not been fully disclosed.
Will existing projects using Radix need to be migrated?
Potentially, yes. Projects relying on Radix as the default may require adjustments to align with the new default settings or to migrate to Base UI components, depending on the project’s configuration and needs.
Why did the developers switch the default framework?
The maintainers cited reasons such as streamlining the architecture, aligning with modern design trends, and improving integration with Base UI, which is increasingly popular among React developers.
Is this change permanent or temporary?
The change appears to be a permanent update, aimed at shaping the future direction of Shadcn/UI. However, the maintainers have not explicitly stated whether Radix support will be phased out or retained as an option.
How will this affect new and existing projects?
New projects will default to Base UI, potentially simplifying setup. Existing projects may need to adjust their configurations if they relied on Radix defaults, but specific migration guidance has not yet been issued.
Source: hn
