Weave Code
Unicon Laravel Laravel Package
unicon-rocks/unicon-laravel
Unicon Laravel integrates the Unicon icon library with Laravel, offering Blade components, helpers, and configuration to render and manage SVG icons from popular icon sets. It streamlines icon usage in views, letting you drop icons into templates without repetitive markup or setup.
:unicorn: Universal icon component for Laravel
Frequently asked questions about Unicon Laravel
- How do I install unicon-rocks/unicon-laravel in a Laravel app?
- Install the package with Composer using composer require unicon-rocks/unicon-laravel. The service provider is auto-discovered, so no manual registration is normally needed, and the configuration file is publishable with the standard vendor:publish command. A first working render typically takes well under a day for a developer already comfortable with Blade components: install, publish config, choose your icon set, then render one component and inspect the output.
- Which Laravel and PHP versions does Unicon Laravel support?
- Supported versions are declared in the package's composer.json constraints and validated by its CI matrix, so check those rather than relying on the README alone. Because the package is a presentation-layer utility with no database or queue surface, version support is usually wide, but confirm the tested matrix before committing to it for an older or brand-new Laravel release. If your application runs an LTS or an unreleased major, verify CI coverage for that combination first.
- How do I render an icon in a Blade template with Unicon Laravel?
- Use the package's Blade component, for example <x-unicon name="..." />, and the package resolves the glyph from your configured icon set instead of you pasting raw SVG markup. This removes repetitive inline SVG from templates and keeps icon usage consistent across views. You can also use the provided helpers when you need to build icon markup outside a typical component call.
- Which icon sets ship with Unicon Laravel, and what licences apply to them?
- The package wraps the Unicon icon library, which aggregates glyphs from popular icon sets; the exact sets included and whether any are opt-in downloads should be confirmed against the repository. Licensing is the item most often missed: a permissively licensed MIT wrapper does not make the bundled glyphs permissive, and icon sets can carry attribution requirements, non-commercial clauses, or free-tier versus pro-tier splits. Treat licence review of the specific sets you standardise on as a compliance task before anything reaches production.
- How do I publish and configure the Unicon config file?
- Publish the package configuration with php artisan vendor:publish and select the Unicon provider, then edit the published file to choose your default icon set and any path or rendering options. Configuration is where you make the design-system decisions, such as which sets are available and how icon names map to your design language. Commit the published config so environments stay consistent.
- Does Unicon Laravel work with Livewire, Inertia or Vue?
- It composes cleanly with Livewire, since icons are simply rendered server-side in Blade. Inertia and Vue applications get little value because rendering happens in Blade rather than in the JavaScript layer, so those stacks should generally not adopt it. It has no Vite or Tailwind dependency, which means no bundler rebuild is required for Blade-based apps.
- How do I make icons accessible with aria-hidden or a title attribute?
- Icons are either decorative, in which case they should be hidden from assistive technology, or meaningful, in which case they need an accessible name. Verify rather than assume whether the component defaults to aria-hidden and whether it exposes a title or label attribute. Also confirm that arbitrary attributes such as class, width and data-* pass through to the rendered SVG, because getting this wrong ships a WCAG regression at scale.
- Can I use Unicon Laravel alongside blade-ui-kit/blade-icons or Filament?
- Technically yes, but check for overlap first, because running two icon systems is the most common way icon handling turns into technical debt. If your application already uses Blade UI Kit or a component library like Filament, decide on a single source of truth for glyphs before adding another layer. A useful mitigation is wrapping Unicon once in an internal component so call sites stay swappable.
- Is Unicon Laravel safe to depend on in production given its small contributor base?
- The technical blast radius is low: it is a presentation-layer utility with no database surface, no queued work and no external service calls, so adopting it in one feature does not commit the wider application. The vendor risk is moderate, since a small star count and contributor base means bus-factor exposure. That risk is substantially mitigated by the MIT licence and small code surface, which make a fork or vendored copy a realistic contingency rather than a rewrite.
- How do I migrate existing icon fonts or hardcoded SVGs to Unicon Laravel?
- Audit your current sources first, because webfonts like Font Awesome, image sprites and hand-pasted SVG partials each need a different swap mechanic. Greenfield surfaces can adopt the component directly with no migration cost, which is the low-risk way to trial it. Budget a manual sweep for existing usage and wrap the package in an internal component so that hundreds of templates do not reference the vendor component name directly.
Weaver
How can I help you explore Laravel packages today?