Shadcn/UI Now Defaults To Base UI Instead Of Radix

Shadcn/UI has officially shifted its default component library from Radix UI to Base UI, a move confirmed by the project maintainers. This change impacts developers who integrate Shadcn/UI into their projects, altering the initial setup and potentially the user experience. The update reflects a strategic direction by the maintainers to streamline the framework’s dependencies and improve developer experience.

According to the official Shadcn/UI documentation and GitHub repository, the default setup now initializes with Base UI components instead of Radix UI. This transition was announced in a recent update, with maintainers clarifying that the change aims to simplify the integration process and reduce external dependencies.

Developers who previously relied on Radix UI for accessibility and interaction primitives will now find Base UI as the default, though Radix remains available as an optional package. The switch is part of a broader effort to unify the UI toolkit and enhance performance.

There is no indication that the core functionality of Shadcn/UI has changed significantly; rather, the default configuration now favors Base UI, which is designed to be more lightweight and easier to customize. The maintainers have emphasized that existing projects using Radix can continue to do so without disruption.

Implications for Developers Adopting Shadcn/UI

This change is significant because it influences how new projects are initialized and configured. Developers now starting with Shadcn/UI will default to Base UI components, which may require adjustments if they previously depended on Radix UI primitives. It also signals a strategic shift toward a more streamlined, dependency-light framework that could influence future updates and community contributions.

For existing projects, the transition should be smooth, as Radix remains available as an optional package. However, teams may need to update their documentation and workflows to align with the new default setup, especially if they are customizing or extending the base components.

Background of Shadcn/UI and Its Dependencies

Shadcn/UI is a popular open-source React component framework that simplifies building accessible, customizable user interfaces. Originally, it integrated Radix UI for interaction primitives like dialogs, sliders, and menus, leveraging Radix’s accessibility features.

Recently, the project maintainers announced a shift to make Base UI the default component library, citing reasons such as reducing external dependencies and improving performance. Radix UI remains available but is no longer the default choice for new projects.

This change reflects ongoing trends in the React ecosystem, where lightweight, customizable component libraries are gaining favor over more complex, dependency-heavy options.

“The switch to Base UI as the default is aimed at streamlining the developer experience and reducing external dependencies.”

— Shadcn/UI Maintainers

Unresolved Questions About Future Development

It is not yet clear how this change will influence future updates to Shadcn/UI or whether additional features will be integrated into Base UI. The long-term roadmap remains unspecified, and community feedback on the switch is still emerging.

Details about how this shift might impact third-party integrations or customizations are also still developing, and some developers may need to adapt their workflows accordingly.

Next Steps for Developers and Project Roadmap

Developers should review the updated documentation to understand the new default setup and adjust their projects as needed. The maintainers are expected to release further updates and possibly new features centered around Base UI.

Community discussions and feedback will likely influence subsequent development, including potential improvements to Base UI or options to revert to Radix if desired. Monitoring the project’s GitHub repository and official channels will be essential for staying informed about future changes.

Key Questions

Does this mean Radix UI is deprecated?

No. Radix UI remains available as an optional package for those who prefer or require its features. The change only affects the default setup in Shadcn/UI.

Will existing projects using Radix UI be affected?

Not directly. Existing projects that use Radix UI as their primary library will continue to function normally. They can also switch to Base UI if they choose to adopt the new default.

Why did the developers make this change?

The maintainers stated that the switch aims to simplify the framework, reduce external dependencies, and improve performance for new projects.

Are there plans to add new features to Base UI?

Details about upcoming features are not yet publicly available. Developers are encouraged to follow official channels for future updates.

How can I revert to Radix UI if I prefer?

Radix UI remains available as an optional package, so developers can manually include and configure it in their projects if they prefer the previous setup.

Source: hn