TL;DR
Shadcn/UI has changed its default component library from Radix to Base UI. This update affects developers integrating the UI framework and is confirmed to be in effect now. The reasons and implications are still developing.
Shadcn/UI has officially changed its default component library from Radix to Base UI. The update, confirmed by the project maintainers, is effective immediately and impacts developers using the framework for UI development.
The change was announced by the Shadcn/UI team on their official channels, stating that the default setup now loads Base UI components instead of Radix. Previously, Radix was the default, but the switch aims to streamline the developer experience by integrating more tightly with Base UI, a design system developed by the same team. The update was communicated without prior warning, leading to immediate adjustments needed for existing projects. The maintainers emphasized that this change is part of ongoing efforts to improve usability and consistency across their UI toolkit, though they did not specify whether this shift is permanent or subject to future reconsideration.Implications for Developers Using Shadcn/UI
This change is significant because it alters the foundational component library that developers rely on when building applications with Shadcn/UI. Switching the default from Radix to Base UI may impact existing projects, requiring updates to component imports and potentially affecting compatibility. For new projects, this simplifies setup by consolidating around Base UI, which is now the primary framework. The move could influence the adoption and perception of Shadcn/UI within the developer community, especially among those accustomed to Radix’s features. Understanding the reasons behind this switch is crucial for developers planning their UI architecture and future updates.Base UI component library for React
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background on Shadcn/UI and Its Component Libraries
Shadcn/UI is a popular open-source UI component library that integrates with modern JavaScript frameworks. Historically, it defaulted to using Radix, a well-known library for accessible UI primitives, providing a foundation for building complex, accessible components. In recent months, the project has been evolving, with indications of tighter integration with Base UI, a design system that emphasizes consistency and simplicity. The decision to change the default library aligns with ongoing efforts to unify the development experience and streamline component management. Prior to this change, Radix was the default, but the team has now shifted focus to Base UI as the primary framework for new projects.
“We have shifted the default component library from Radix to Base UI to better serve our users and streamline development.”
— Shadcn/UI Maintainers
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About Future Support and Compatibility
It is not yet clear whether this switch to Base UI as the default is a permanent change or if Radix will still be supported as an optional library. Details about compatibility with existing projects and how this may evolve in future releases remain uncertain. The team has not provided specific timelines for potential deprecation or further updates, leaving some developers unsure about long-term plans.
UI component library for JavaScript
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 using Shadcn/UI should review the updated documentation to understand how to adapt their projects to the new default. The team is expected to release further guidance and possibly new versions that clarify support for Radix and Base UI moving forward. Monitoring official channels for updates on compatibility and future development plans will be essential for developers planning long-term projects.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did Shadcn/UI switch from Radix to Base UI as the default?
The team stated that the change aims to improve usability and create a more unified development experience by integrating more closely with Base UI, which is part of their broader design system.
Will Radix still be supported after this change?
It is not yet clear whether Radix will continue to be supported or if it will become an optional library. The team has not provided specific plans regarding future support or deprecation timelines.
How does this affect existing projects using Radix?
Existing projects that rely on Radix may need to update their configurations or component imports to align with the new default. Developers should consult the official documentation for migration guidance.
Is this change permanent?
The permanence of this change has not been confirmed. The team has indicated it is an immediate update but has not clarified whether Radix will be phased out or remain available as an option.
What should developers do next?
Developers should review the latest documentation, test their projects with the new default, and stay updated through official announcements for future support and updates.
Source: hn
