Vue

For @devigner-ui/icons-vue, which jumps from 2.x to 3.5.0 to share one version with the other packages. Nothing in it breaks. Upgrade, then run the codemod, which ships in the React package and works on .vue files too:

Terminal
npm install @devigner-ui/icons-vue@^3.5.0
npx @devigner-ui/icons migrate

Old names keep working

Every old name is still exported and renders the renamed icon, with the same props and attribute fallthrough:

HTML
<script setup>
import { IconBag2 } from "@devigner-ui/icons-vue";       // still works
import { IconBagStraps } from "@devigner-ui/icons-vue";  // the new name
</script>

In development an old name logs one warning in the browser console, naming its replacement. Production builds are silent. Old names are marked @deprecated in the types, so Volar and your editor strike them through.

What the codemod cannot see

Icons chosen at runtime, such as a component name stored in your data or passed to <component :is> as a string. Map stored names once with renames.json; see the codemod page.

Old names stop working in 4.0.0

See Upcoming 4.0.

Documentation

Browse all 12,480 icons