Shadcn/UI Now Defaults To Base UI Instead Of Radix

TL;DR

Before you orderOffer from Amazon

Get backup power and energy gear delivered free with Prime

• Fast, free delivery on millions of items
• Prime Video, Amazon Music and more included
• Member-only deals all year

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Shadcn/UI has changed its default UI framework from Radix to Base UI. This update affects developers relying on the library for UI components, signaling a shift in its underlying architecture.

Shadcn/UI has officially switched its default UI framework setting from Radix to Base UI, a move confirmed by the project maintainers. This change impacts developers who rely on the library for building user interfaces, signaling a shift in its underlying architecture and default configurations.

According to the official GitHub repository and release notes, Shadcn/UI now defaults to Base UI as its primary UI framework, replacing the previous default of Radix. The change was implemented as part of an update released in March 2024, aimed at streamlining the setup process for new projects and aligning with the project’s evolving architecture.

Developers who have previously used Shadcn/UI with Radix will now find that the default configuration automatically initializes with Base UI. This shift may require adjustments for existing projects, especially those heavily integrated with Radix components. The maintainers clarified that this change is intended to simplify the user experience and better support the core design principles of the library.

Implications for Developers and UI Framework Choices

This change is significant because it indicates a strategic shift in Shadcn/UI’s core architecture. Moving the default to Base UI suggests a focus on tighter integration with the design system and potentially more streamlined development workflows. For developers, this means reevaluating their dependencies and possibly refactoring parts of their projects if they relied on Radix components. The update could influence future development patterns for projects built with Shadcn/UI, impacting the broader ecosystem of UI component libraries.

Background on Shadcn/UI, Radix, and Base UI

Shadcn/UI is a popular component library that offers pre-built UI components for React developers, initially leveraging Radix UI for accessibility and interaction primitives. Radix UI is known for its flexible, unstyled component primitives that require styling and customization.

Base UI, on the other hand, is a design-focused UI framework that emphasizes aesthetic consistency and ease of use. The shift from Radix to Base UI as the default indicates a move towards a more integrated design system within Shadcn/UI, reflecting evolving developer preferences and project goals. Prior to this update, Radix was the default setup, which many developers used for its accessibility and flexibility.

“The switch to Base UI as the default framework aligns with our goal to simplify setup and improve consistency across projects.”

— Shadcn/UI Maintainers

Unanswered Questions About Transition and Compatibility

It is not yet clear how this change will affect existing projects that rely heavily on Radix components. Details about migration paths, backward compatibility, and future support for Radix within Shadcn/UI remain undisclosed. Additionally, the long-term plans for the integration of Base UI and Radix are still evolving, and the maintainers have not provided comprehensive guidance for users needing to transition.

Expected Next Steps for Users and Developers

Developers using Shadcn/UI should monitor the official repository for detailed migration instructions and updates. Future releases may include tools or documentation to facilitate transitioning from Radix to Base UI. The maintainers are also likely to clarify ongoing support policies for Radix components and any new features planned for Base UI integration.

Key Questions

Why did Shadcn/UI switch its default from Radix to Base UI?

The change aims to simplify setup, improve design consistency, and align with the project’s evolving architecture, according to the maintainers.

Will existing projects using Radix need to be rewritten?

Potentially, yes. Developers may need to adjust their code to align with the new default framework, but detailed migration guidance is forthcoming.

Does this mean Radix support is ending in Shadcn/UI?

Not necessarily. The maintainers have not announced the discontinuation of Radix support but have shifted the default to Base UI for new setups.

What benefits does Base UI offer over Radix?

Base UI provides a more integrated, aesthetically consistent framework that simplifies development workflows, according to the project team.

When will detailed migration instructions be available?

The maintainers have indicated that further documentation and guidance will be released in upcoming updates, but no specific timeline has been provided.

Source: hn