Weave Code
Blade Uiw Icons Laravel Package
codeat3/blade-uiw-icons
Blade UIW Icons brings the UIW icon set to Laravel Blade as simple, cacheable components like . Install once, then drop any icon into your views with a single tag—no SVGs to copy, no extra setup, just clean, consistent icons across your app.
A package to easily make use of Uiw Icons in your Laravel Blade views.
Frequently asked questions about Blade Uiw Icons
- How do I install codeat3/blade-uiw-icons in a Laravel app?
- Run composer require codeat3/blade-uiw-icons. The package depends on blade-ui-kit/blade-icons, which is pulled in automatically, and its Blade components are registered through Laravel package discovery with no manual service provider edits. Optionally publish the config file if you need to change the component prefix or default CSS class.
- Which Laravel versions does blade-uiw-icons support?
- Release 1.7.0 widened the framework constraint to cover Laravel 10 through Laravel 13. That release was a semver-correct constraint change with no breaking changes, no new icons, and no deprecation churn. Check the repository CI matrix for the exact PHP floor rather than assuming it from the docs.
- How do I use a UIW icon inside a Blade view?
- Drop the component tag directly into your markup, for example x-uiw- followed by the icon name, and it renders inline SVG. Because it is inline SVG, it inherits currentColor and any Tailwind text color utilities already applied by a parent element. No JavaScript, icon font, or asset build step is required.
- How do I find the correct icon name for a UIW icon?
- Names map to the SVG filenames shipped in the package's resources/svg directory, which is a snapshot of the Unicons icon set. Grep that folder or browse the upstream Unicons gallery to confirm a name. Because the packaged snapshot can lag upstream additions and renames, always verify the name against the installed version rather than the live website.
- How do I change the component prefix or the default CSS class?
- Publish the package config and set the prefix and default class values there. This also matters when you already use another codeat3/blade-* icon package, since matching prefixes can collide; resolve them at config-publish time. Keep a single mapping file of semantic names to Uiw names so swapping icon sets later stays cheap.
- Does blade-uiw-icons work with Tailwind CSS and currentColor?
- Yes. Icons are rendered as inline SVG that inherit currentColor, so existing text-* color utilities and hover states apply without extra configuration. You can also apply size classes directly to the component tag. There is no second icon runtime or font loader to reconcile with your Tailwind setup.
- How do I cache icons for production performance?
- Run php artisan icons:cache as part of your deploy pipeline to avoid re-resolving icon sets on every request. This is the standard blade-icons caching command and helps most on icon-dense pages where inline SVG response size grows. Re-run it whenever icons are added or the package is upgraded, and clear it if names stop resolving.
- Can I use blade-uiw-icons with Inertia, Vue, or React?
- It is a poor fit there. Those stacks would need the icon set carried in both PHP and JavaScript, creating duplicate payload and a second upgrade surface. Use @uiw/icons directly in the JS layer instead, and reserve this package for server-rendered Blade and Livewire views.
- What happens if codeat3/blade-uiw-icons is abandoned by its maintainer?
- Risk is low because the artifact is static SVG plus a thin registration layer, with no runtime service, persistence, or domain logic. If maintenance stops, fork the repository and vendor it into your app in hours, or point the same component names at a self-managed SVG folder. Decide up front who owns that contingency and what triggers it, such as a missed Laravel major release.
- How do I test that UIW icons render correctly in my Blade views?
- Render the view in a feature test and assert the expected SVG markup or icon identifier is present, for example with assertSee on a stable path or class. Keep tests on your own semantic component names rather than raw Uiw filenames so upstream renames surface in one place. Also assert the icons:cache command runs in CI so production caching does not silently break resolution.
Weaver
How can I help you explore Laravel packages today?