Oxide Icons

Oxide Icons

An icon library that knows where it is.
Native Web Component, zero dependencies, and the only icon system built around explicit isolation between visual icon families in the same application. Stop debugging why the wrong icon style leaked into a section of your app that was never supposed to see it.

Phase 3 of 4: writing Getting Started against the real package. Architecture, runtime, and the 104-icon catalog are done. See phases below.

Ler em Português

--- ## The problem it solves Every popular icon library, Lucide, Heroicons, Feather, solves "give me an icon" well. None of them solve the problem of two icon families coexisting in the same application without bleeding into each other by accident: a dashboard using an "outline" icon set that accidentally inherits a "filled" icon from another dependency, or a design system that needs to guarantee a section of the app never mixes styles. Oxide Icons solves this with a context and isolation system: zones of the application declare which family they belong to, and the library decides, predictably and configurably (`soft` / `exclusive` / `strict`), what happens when an icon from outside shows up there. ```html
``` Read more: [How Oxide Icons thinks about icons](./docs/concepts.md). ## What's already built - Native Web Component (``), zero runtime dependencies. - On-demand (JIT) loading, per icon family. - Context and isolation system (`soft`/`exclusive`/`strict`). - Strict-mode TypeScript from the first file. - Contract-driven architecture, documented in Architecture Decision Records before any implementation. - 104 icons across 11 families (`ui`, `arrows`, `actions`, `navigation`, `files-folders`, `communication`, `media`, `devices`, `commerce`, `security`, `weather`) and a working browser example wiring everything end to end. ## Development phases The package is already published and usable. The project is still in active development, with four phases covering the catalogue, documentation, and future releases: 1. **Architecture and runtime**: done. Domain contracts, the isolation system, ``, the Vite plugin, all built against real tests, not sketched. 2. **Icon catalog**: done. All 11 planned families are built: `UI Essentials`, `Actions`, `Navigation`, `Files & Folders`, `Communication`, `Media`, `Devices`, `Commerce`, `Security`, `Weather`, `Arrows` (104 icons). Coverage, not a count, is the finish line, see the note below. 3. **Getting Started, written against the real package**: the guide is being built around the package that is already available. 4. **Release and iteration**: continue improving the catalogue, documentation, tests, and package releases. We're not chasing "5000 icons" as a launch number. A useful, coherent set beats an arbitrary one, what differentiates this project is the architecture, not the catalog size. ## Current status Oxide Icons is already published and can be installed and used in a project. The package is still evolving, so the current release should be seen as an early version rather than a finished catalogue. An earlier version of the project was abandoned during a refactor. Instead of continuing from that codebase, we restarted with the architecture defined and documented before implementation. The current package is the result of that restart and is already being used in a test project. ## Follow development Code, tests, and architecture decisions live in the development repository. ## License MIT, see [LICENSE](./LICENSE).