Iconizza is the most versatile icon framework.
For more information visit https://iconizza.design/.
There are several parts of project, some are in this repository, some are in other repositories.
What is included in this repository?
packages contains main reusable packages: types, utilities, reusable functions used by various components.iconizza-icon contains iconizza-icon web component that renders icons. It also contains wrappers for various frameworks that cannot handle web components.components contains older version of icon components that are native to various frameworks, which do not use web component.plugins contains plugins for various frameworks, which generate icons.Other repositories you might want to look at:
iconizza/icon-sets repository.iconizza/tools repository.Main packages in this repository are various icon components.
Why are those icon components needed? Iconizza icon components are not just yet another set of icon components. Unlike other icon components, Iconizza icon components do not include icon data. Instead, icon data is loaded on demand from Iconizza API.
Iconizza API provides data for over 200,000 open source icons! API is hosted on publicly available servers, spread out geographically to make sure visitors from all over the world have the fastest possible connection with redundancies in place to make sure it is always online.
When you use an icon font, each visitor loads an entire font, even if your page only uses a few icons. This is a major downside of using icon fonts. That limits developers to one or two fonts or icon sets.
If you are using typical icon set that is not a font, you still need to bundle all icons used in your application, even ones that visitor does not need.
Unlike icon fonts and components for various icon sets, Iconizza icon components dynamically load icon data from Iconizza API whenever it is needed.
This makes it possible to have an unlimited choice of icons!
There are several types of packages, split in their own directories.
Directory packages contains main packages that are reusable by all other packages in this repository as well as third party components.
Main packages:
Directory iconizza-icon contains iconizza-icon web component and wrappers for various frameworks.
| Package | Usage |
|---|---|
| Web component | Everywhere |
| React wrapper | React |
| SolidJS wrapper | SolidJS |
Frameworks that are confirmed to work with web components without custom wrappers:
class instead of className. Wrapper fixes it and provides types.Directory iconizza-icon-demo contains demo packages that show usage of iconizza-icon web component.
npm run build to build demo and npm run start to start it.npm run dev to start demo.npm run dev to start demo.npm run dev to start demo.npm run dev to start the demo.npm run dev to start demo.npm run dev to start demo. Requires custom config, see below.npm run build to build demo and npm run serve to start it.npm run dev to start demo.npm run start to start demo.When using web component with Nuxt 3, you need to tell Nuxt that iconizza-icon is a custom element. Otherwise it will show few errors.
Example nuxt.config.ts:
import { defineNuxtConfig } from 'nuxt3'
export default defineNuxtConfig({
vue: {
compilerOptions: {
isCustomElement: tag => tag === 'iconizza-icon',
},
},
})
This configuration change is not needed when using Vue with @vitejs/plugin-vue.
Directory components contains Iconizza icon components and SVG framework.
| Package | Usage |
|---|---|
| SVG Framework | HTML |
| React component | React |
| Vue 3 component | Vue 3 |
| Vue 2 component | Vue 2 |
| Svelte component | Svelte |
| Ember component | Ember |
Components in directory components are slowly phased out in favor of iconizza-icon web component. Components are still maintained and supported, but it is better to switch to web component.
Functionality is identical, but web component has some advantages:
Deprecation status:
iconizza-icon.iconizza-icon using @iconizza-icon/react wrapper.iconizza-icon, does not require Svelte specific wrapper.iconizza-icon, does not require Vue specific wrapper.iconizza-icon, does not require Vue specific wrapper. Make sure you are not using Webpack older than version 5.iconizza-icon, does not require Ember specific wrapper.To import web component, just import it once in your script, as per iconizza-icon README file.
Directory components-demo contains demo packages that show usage of icon components.
npm run dev to start demo.npm run dev to start demo.npm run dev to start demo.npm run dev to start demo.npm run build to build demo and npm run serve to start it.npm run dev to start demo.npm run dev to start demo.npm run dev to start the demo.npm run build to build demo and npm run start to start it.Directory plugins contains plugins.
| Package | Usage |
|---|---|
| Tailwind CSS plugin | Tailwind CSS |
Directory plugins-demo contains demo packages that show usage of plugins.
npm run build to build demo, open src/index.html in browser to see result.See CONTRIBUTING.md.
Documentation for all packages is available on Iconizza documentation website:
Iconizza is licensed under MIT license.
SPDX-License-Identifier: MIT
Some packages of this monorepo in previous versions were dual-licensed under Apache 2.0 and GPL 2.0 licence, which was messy and confusing. This was later changed to MIT for simplicity.
This licence does not apply to icons. Icons are released under different licences, see each icon set for details. Icons available by default are all licensed under various open-source licences.
© 2020-PRESENT Dennis Ollhoff