Loading...
You do not need a big-bang migration. Move one icon—or one feature—at a time.
Search the icon explorer, compare variants, and note the exact @collection/icon ID. Similar names do not always mean identical shapes.
Update styling and accessibility labels as needed, then compare the rendered result at every size and state your UI uses.
Search the repository for remaining imports. Remove the previous icon package only when none remain, and verify your normal web or native production build.
Rocketicons keeps shared utilities installed, but the selected icon components live in your source tree. The benefit is structural: your application never imports thousands of unused icon exports and does not rely on tree-shaking to discard them.