migrate-radix-to-base

Run the migration component by component: classify each ui wrapper against its stock registry origin, fetch the base-style variant, replay your customizations with a three-way merge, then repoint consumers one at a time. Radix dependencies are removed only after the last component is migrated.

Use progressive mode: the migrated version is written to accordion-base.tsx while the original stays untouched, consumers are repointed one at a time with typechecks, and the original is deleted once nothing imports it. The files on disk track progress, so interrupted migrations resume automatically.

Base UI replaces asChild with the render prop, which accepts a React element or a function of props and state. For example, <Trigger asChild><Button/></Trigger> becomes <Trigger render={<Button/>}>, and button-like parts accept nativeButton when the render target is not a native button.

No. AspectRatio maps to the CSS aspect-ratio property, Label to a native label element, VisuallyHidden to the sr-only class, and Direction to a DirectionProvider with a direction prop. Popover Anchor and NavigationMenu Indicator have no equivalent and are flagged as inert passthroughs.

Non-Radix libraries such as cmdk (command), vaul (drawer), sonner, input-otp, react-day-picker (calendar), and recharts (chart) are never modified. They are reported as intentionally untouched in the per-component migration reports.

Known deltas include tabs defaulting to manual activation, menu checkbox and radio items not closing on click by default, and NavigationMenu hover delay changing from 200ms to 50ms. These are flagged in the migration report rather than silently patched.