Which frameworks does xicons support?

Updated

xicons supports Vue and React. That is the scope stated in the site's own title, "xicons - Icons for Vue & React," and it is the main compatibility fact to check before adopting it. If your project is built on either framework, xicons is aimed at you. If you are working in Angular, Svelte, Solid, plain web components, or a server-side template system, the icons are not presented as framework-specific packages for those environments, so you should not assume a drop-in component will exist.

What "supports Vue and React" means in practice

The useful reading of that statement is that the icon set is distributed in forms meant to be consumed inside Vue and React projects. In other words, the project is not just a folder of raw SVG files with a generic download link; it is organized around the two frameworks named on the site.

That distinction matters because it changes what you get:

  • Vue projects — the icons are intended to be used as part of a Vue component workflow.
  • React projects — the icons are intended to be used as part of a React component workflow.
  • Other frameworks — there is no stated first-class integration, so you would be adapting the assets yourself rather than following the project's intended path.

How to confirm it fits your project

Before you commit to xicons, run through this short check:

  1. Identify your framework. Is the app actually Vue or React? A project using Vue via a wrapper, or React inside a larger non-React shell, still counts, but the icon usage will live in the Vue/React part.
  2. Check your build setup. Confirm you can consume the icon package the way the project expects for your framework. If your toolchain already handles Vue or React components, you are in the supported lane.
  3. Verify with one icon first. Add a single icon and render it. If it appears correctly, the integration path works for your setup; if not, the problem is usually the import style or build config rather than the icon set itself.
  4. Decide for non-Vue/React stacks. If your framework is neither, treat xicons as a source of icon assets you would need to convert, not as a ready-made library.

When xicons is the wrong choice

You should look elsewhere if any of these apply:

  • Your project is not Vue or React and you want framework-native icon components out of the box.
  • You need a single icon solution that spans several frameworks with equal, documented support.
  • You require guarantees about framework versions, tree-shaking behavior, or long-term maintenance that the site does not state.

The site's title is the clearest signal available: it names Vue and React and nothing else. Treat that as the boundary of what is officially supported, and confirm your own framework against it before building xicons into your project.