# unplugin-icons [![NPM version](https://img.shields.io/npm/v/unplugin-icons?color=a1b858&label=)](https://www.npmjs.com/package/unplugin-icons) Access thousands of icons as components **on-demand** universally. ### Features - ๐ŸŒ Universal - ๐Ÿคน **Any** icon sets - 100+ popular sets with over 10,000 icons, logos, emojis, etc. Powered by [Iconify](https://github.com/iconify/iconify). - ๐Ÿ“ฆ **Major** build tools - Vite, Webpack, Rollup, Nuxt, etc. Powered by [unplugin](https://github.com/unjs/unplugin). - ๐Ÿชœ **Major** frameworks - Vanilla, Web Components, React, Vue 3, Vue 2, Solid, Svelte, and more. [Contribute](./src/core/compiles). - ๐Ÿฑ **Any** combinations of them! - โ˜๏ธ On-demand - Only bundle the icons you really use, while having all the options. - ๐Ÿ–จ SSR / SSG friendly - Ship the icons with your page, no more FOUC. - ๐ŸŒˆ Stylable - Change size, color, or even add animations as you would with styles and classes. - ๐Ÿ“ฅ [Custom icons](#custom-icons) - load your custom icons to get universal integrations at ease. - ๐Ÿ“ฒ [Auto Importing](#auto-importing) - Use icons as components directly in your template. - ๐Ÿฆพ TypeScript support. - ๐Ÿ” [Browse Icons](https://icones.js.org/)

   ๐Ÿ’ก **Story behind this tool**: [Journey with Icons Continues](https://antfu.me/posts/journey-with-icons-continues) - a blog post by Anthony   
> **`vite-plugin-icons` has been renamed to `unplugin-icons`**, see the [migration guide](#migrate-from-vite-plugin-icons) ## Usage Import icons names with the convention `~icons/{collection}/{icon}` and use them directly as components. [Auto importing is also possible](#auto-importing). ###### React ```jsx import IconAccessibility from '~icons/carbon/accessibility' import IconAccountBox from '~icons/mdi/account-box' function App() { return (
) } ``` ###### Vue ```html ``` ## Install ### Plugin ```bash npm i -D unplugin-icons ``` ### Icons Data We use [Iconify](https://iconify.design/) as the icons data source (supports 100+ iconsets). You have two ways to install them: ###### Install Full Collection ```bash npm i -D @iconify/json ``` `@iconify/json` (~120MB) includes all the iconsets from Iconify so you can install once and use any of them as you want (only the icons you actually use will be bundle into the production build). ###### Install by Icon Set If you only want to use a few of the icon sets and don't want to download the entire collection, you can also install them individually with `@iconify-json/[collection-id]`. For example, to install [Material Design Icons](https://icon-sets.iconify.design/mdi/), you can do: ```bash npm i -D @iconify-json/mdi ``` To boost your workflow, it's also possible to let `unplugin-icons` handle that installation by enabling the `autoInstall` option. ```ts Icons({ // experimental autoInstall: true, }) ``` It will install the icon set when you import them. The right package manager will be auto-detected (`npm`, `yarn` or `pnpm`). ## Configuration ###### Build Tools
Vite
```ts // vite.config.ts import Icons from 'unplugin-icons/vite' export default defineConfig({ plugins: [ Icons({ /* options */ }), ], }) ```
Rollup
```ts // rollup.config.js import Icons from 'unplugin-icons/rollup' export default { plugins: [ Icons({ /* options */ }), ], } ```
Webpack
```ts // webpack.config.js module.exports = { /* ... */ plugins: [ require('unplugin-icons/webpack')({ /* options */ }), ], } ```
Nuxt
Nuxt 2 and [Nuxt Bridge](https://github.com/nuxt/bridge) ```ts // nuxt.config.js export default { buildModules: [ ['unplugin-icons/nuxt', { /* options */ }], ], } ``` Nuxt 3 ```ts // nuxt.config.js export default defineNuxtConfig({ modules: [ ['unplugin-icons/nuxt', { /* options */ }] ], }) ```
Vue CLI
```ts // vue.config.js module.exports = { configureWebpack: { plugins: [ require('unplugin-icons/webpack')({ /* options */ }), ], }, } ```
SvelteKit
The `unplugin-icons` plugin should be configured in the `vite.config.js` configuration file: ```ts // vite.config.js import { defineConfig } from 'vite' import { sveltekit } from '@sveltejs/kit/vite' import Icons from 'unplugin-icons/vite' export default defineConfig({ plugins: [ sveltekit(), Icons({ compiler: 'svelte', }) ] }) ``` Check instructions in the `Frameworks -> Svelte` section below if you faced module import errors.
Svelte + Vite
Svelte support requires the `@sveltejs/vite-plugin-svelte` plugin: ```shell npm i -D @sveltejs/vite-plugin-svelte ``` The `unplugin-icons` plugin should be configured in the `vite.config.js` configuration file: ```ts // vite.config.js import { defineConfig } from 'vite' import { svelte } from '@sveltejs/vite-plugin-svelte' import Icons from 'unplugin-icons/vite' export default defineConfig({ plugins: [ svelte(), Icons({ compiler: 'svelte', }), ], }) ``` Check instructions in the `Frameworks -> Svelte` section below if you faced module import errors.
Next.js
The `unplugin-icons` plugin should be configured on `next.config.js` configuration file: ```js /** @type {import('next').NextConfig} */ module.exports = { reactStrictMode: true, webpack(config) { config.plugins.push( require('unplugin-icons/webpack')({ compiler: 'jsx', jsx: 'react', }), ) return config }, } ``` Check instructions in the `Frameworks -> React` section below if you faced module import errors. โš ๏ธ **Warning:** to import an icon is necessary to explicitly add the `.jsx` extension to the import path, so that Next.js knows how to load it, by example: ```ts import IconArrowRight from '~icons/dashicons/arrow-right.jsx'; // ^-- write `.jsx` to avoid // https://github.com/antfu/unplugin-icons/issues/103 // ...some code later ``` See inside of `examples/next` for a working example project.
esbuild
```ts // esbuild.config.js import { build } from 'esbuild' build({ /* ... */ plugins: [ require('unplugin-icons/esbuild')({ /* options */ }), ], }) ```
Astro
```ts // astro.config.mjs import { defineConfig } from 'astro/config' import Icons from 'unplugin-icons/vite' // https://astro.build/config export default defineConfig({ vite: { plugins: [ Icons({ compiler: 'astro', }), ], }, }) ```
###### Frameworks
Vue 3 / Vue 2.7+
Vue 3 / Vue 2.7+ support requires peer dependency `@vue/compiler-sfc`: ```bash npm i -D @vue/compiler-sfc ``` ```ts Icons({ compiler: 'vue3' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/vue", ] } } ```
Vue 2 (only for versions < 2.7)
Vue 2 support requires peer dependency `vue-template-compiler`: ```bash npm i -D vue-template-compiler ``` ```ts Icons({ compiler: 'vue2' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/vue", ] } } ```
React
JSX support requires peer dependency `@svgr/core` and its plugin `@svgr/plugin-jsx`: ```bash npm i -D @svgr/core @svgr/plugin-jsx ``` ```ts Icons({ compiler: 'jsx', jsx: 'react' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/react", ] } } ```
Preact
JSX support requires peer dependency `@svgr/core` and its plugin `@svgr/plugin-jsx`: ```bash npm i -D @svgr/core @svgr/plugin-jsx ``` ```ts Icons({ compiler: 'jsx', jsx: 'preact' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/preact", ] } } ```
Solid
```ts Icons({ compiler: 'solid' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/solid", ] } } ```
Svelte
```ts Icons({ compiler: 'svelte' }) ``` Type Declarations For SvelteKit, in the `src/app.d.ts` file: ```ts import 'unplugin-icons/types/svelte' ``` For Svelte + Vite, in the `src/vite-env.d.ts` file: ```js /// /// /// ```
Astro
Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/astro", ] } } ```
Qwik
Qwik support requires peer dependency `@svgx/core`: ```bash npm i -D @svgx/core ``` ```ts Icons({ compiler: 'qwik' }) ``` Type Declarations ```jsonc // tsconfig.json { "compilerOptions": { "types": [ "unplugin-icons/types/qwik", ] } } ```
## Use RAW compiler from query params From `v0.13.2` you can also use `raw` compiler to access the `svg` icon and use it on your html templates, just add `raw` to the icon query param. For example, using `vue3`: ```vue ``` ## Custom Icons From `v0.11`, you can now load your own icons! From `v0.13` you can also provide a transform callback to `FileSystemIconLoader`. ```ts import { promises as fs } from 'node:fs' // loader helpers import { FileSystemIconLoader } from 'unplugin-icons/loaders' Icons({ customCollections: { // key as the collection name 'my-icons': { account: '', // load your custom icon lazily settings: () => fs.readFile('./path/to/my-icon.svg', 'utf-8'), /* ... */ }, 'my-other-icons': async (iconName) => { // your custom loader here. Do whatever you want. // for example, fetch from a remote server: return await fetch(`https://example.com/icons/${iconName}.svg`).then(res => res.text()) }, // a helper to load icons from the file system // files under `./assets/icons` with `.svg` extension will be loaded as it's file name // you can also provide a transform callback to change each icon (optional) 'my-yet-other-icons': FileSystemIconLoader( './assets/icons', svg => svg.replace(/^ ๐Ÿ’ก SVG Authoring Tips: > - To make your icons color adaptable, set `fill="currentColor"` or `stroke="currentColor"` in your SVG. > - Leave the `height` and `width` unspecified, we will set them for you. ### Use with Resolver When using with resolvers for auto-importing, you will need to tell it your custom collection names: ```ts IconResolver({ customCollections: [ 'my-icons', 'my-other-icons', 'my-yet-other-icons', ], }) ``` See the [Vue 3 + Vite example](./examples/vite-vue3/vite.config.ts). ## Icon customizer From `v0.13` you can also customize each icon using `iconCustomizer` configuration option or using query params when importing them. The `query` param will take precedence over `iconCustomizer` and `iconCustomizer` over `configuration`. The `iconCustomizer` and `query` params will be applied to any collection, that is, for each icon from `custom` loader, `inlined` on `customCollections` or from `@iconify`. For example, you can configure `iconCustomizer` to change all icons for a collection or individual icons on a collection: ```ts import { promises as fs } from 'node:fs' // loader helpers import { FileSystemIconLoader } from 'unplugin-icons/loaders' Icons({ customCollections: { // key as the collection name 'my-icons': { account: '', // load your custom icon lazily settings: () => fs.readFile('./path/to/my-icon.svg', 'utf-8'), /* ... */ }, 'my-other-icons': async (iconName) => { // your custom loader here. Do whatever you want. // for example, fetch from a remote server: return await fetch(`https://example.com/icons/${iconName}.svg`).then(res => res.text()) }, // a helper to load icons from the file system // files under `./assets/icons` with `.svg` extension will be loaded as it's file name // you can also provide a transform callback to change each icon (optional) 'my-yet-other-icons': FileSystemIconLoader( './assets/icons', svg => svg.replace(/^ ```vue ``` See `src/App.vue` component and `vite.config.ts` configuration on `vite-vue3` example project. ## Global Custom Icon Transformation From version `0.14.2`, when loading your custom icons, you can transform them, for example adding `fill` attribute with `currentColor`: ```ts Icons({ customCollections: { // key as the collection name 'my-icons': { account: '', /* ... */ }, }, transform(svg, collection, icon) { // apply fill to this icon on this collection if (collection === 'my-icons' && icon === 'account') return svg.replace(/^ You can still use `virtual:icons` prefix in Vite if you prefer, but it's not yet supported in Webpack, we are unifying it as a workaround in the docs. ## Options You can set default styling for all icons. The following config shows the default values of each option: ```ts Icons({ scale: 1.2, // Scale of icons against 1em defaultStyle: '', // Style apply to icons defaultClass: '', // Class names apply to icons compiler: null, // 'vue2', 'vue3', 'jsx' jsx: 'react', // 'react' or 'preact' }) ``` ## Auto Importing
Vue 2 & 3

Use with [`unplugin-vue-components`](https://github.com/antfu/unplugin-vue-components) For example in Vite: ```js // vite.config.js import Vue from '@vitejs/plugin-vue' import Icons from 'unplugin-icons/vite' import IconsResolver from 'unplugin-icons/resolver' import Components from 'unplugin-vue-components/vite' export default { plugins: [ Vue(), Components({ resolvers: [ IconsResolver(), ], }), Icons(), ], } ``` Then you can use any icons as you want without explicit importing. Only the used icons will be bundled. ```html ```
React & Solid
Use with [`unplugin-auto-import`](https://github.com/antfu/unplugin-auto-import) For example in Vite: ```js // vite.config.js import Icons from 'unplugin-icons/vite' import IconsResolver from 'unplugin-icons/resolver' import AutoImport from 'unplugin-auto-import/vite' export default { plugins: [ /* ... */ AutoImport({ resolvers: [ IconsResolver({ prefix: 'Icon', extension: 'jsx', }), ], }), Icons({ compiler: 'jsx', // or 'solid' }), ], } ``` Then you can use any icons with the prefix `Icon` as you want without explicit importing. Type declarations will be generated on the fly. ```js export function Component() { return (
) } ```
### Name Conversion When using component resolver, you have to follow the name conversion for icons to be properly inferred. ``` {prefix}-{collection}-{icon} ``` The `collection` field follows [Iconify's collection IDs](https://iconify.design/icon-sets/). By default, the prefix is set to `i` while you can customize via config ```ts IconsResolver({ prefix: 'icon', // <-- }) ``` ```html ``` Non-prefix mode is also supported ```ts IconsResolver({ prefix: false, // <-- // this is optional, default enabling all the collections supported by Iconify enabledCollections: ['mdi'], }) ``` ```vue ``` ### Collection Aliases When using component resolver, you have to use the name of the collection that can be long or redundant: for example, when using `icon-park` collection you need to use it like this ``. You can add an alias for any collection to the `IconResolver` plugin: ```ts IconsResolver({ alias: { park: 'icon-park', fas: 'fa-solid', // ... } }) ``` You can use the alias or the collection name, the plugin will resolve both. Following with the example and configuring the plugin with previous `alias` entry, you can now use `` or ``. ## Sponsors This project is part of my Sponsor Program

## License MIT License ยฉ 2020-PRESENT [Anthony Fu](https://github.com/antfu)