Migrating to radix-ui is very awkward, any suggestions?

[TomerRon]

Hi all,

According to the June 2025 changelog, we should replace all @radix-ui/react-* imports with radix-ui imports. This is a really nice change that cleans up our package.json, and we can run it automatically with the shadcn@latest migrate radix command.

However, this only applies to components that were already installed, not to future components. When we install a new component, it will still use the old @radix-ui/react-* import, and we will need to remember to run the migration command again.

Simple reproduction steps:

• Migrate an existing project to radix-ui by running the command npx shadcn@latest migrate radix
• Observe that all of the imports were updated to radix-ui
• Install a new component with shadcn CLI
• Observe that the new component uses the old @radix-ui/react-* import ❓❓❓

This is really awkward to use, especially when working in a team, and makes us want to not make this migration at all. There is no mention of this change anywhere else, and the base components themselves still use the old imports. How strange!

There may be some creative workarounds - like adding the migrate command as a postinstall script - but we feel that this is just substituting one awkward solution with another.

What are other people's thoughts about this change, and how are you dealing with it?

[HasanMothaffar]

Yep, this migration step is hidden in the changelog, and I came accross it by change. It's difficult to remember to run this command every time you install a new component