Weave Code
Blade Prime Icons Laravel Package
codeat3/blade-prime-icons
Laravel Blade component package for easily rendering PrimeIcons in your views. Use a simple Blade tag to add icons, control size and classes, and keep templates clean—no manual SVG or CSS setup required. Ideal for quickly adding consistent icons to Laravel apps.
A package to easily make use of Prime Icons in your Laravel Blade views.
Frequently asked questions about Blade Prime Icons
- How do I install codeat3/blade-prime-icons in Laravel?
- Install it with Composer by running composer require codeat3/blade-prime-icons. Laravel package auto-discovery registers the service provider, so there are no migrations, no required publish step, and no build-tool changes. You can usually render your first icon in a staging branch in under an hour.
- Does codeat3/blade-prime-icons support Laravel 10, 11, 12, and 13?
- The package is designed for Blade-rendered Laravel apps, and the 1.8.0 changelog mentions Laravel 13 compatibility. Before upgrading, check the composer.json diff to confirm whether 1.8.0 only adds Laravel 13 to the support matrix or also raises the PHP or blade-ui-kit/blade-icons floor. Treat Laravel 13 support as permission to stay current, not as a reason to schedule a framework upgrade early.
- How do I render a PrimeIcons icon in a Laravel Blade view?
- Use the generated Blade component syntax directly in your template, for example <x-prime-icons-user />. The package exposes the PrimeIcons collection as components so you do not need to remember icon CSS classes or manually add SVGs. This keeps icon markup consistent across Blade views, Livewire components, and mail templates.
- Can I customize icon size, color, and CSS classes?
- Yes. The package supports customizing size, color, and extra CSS classes when rendering icons in Blade. Attribute handling and rendering are delegated to blade-ui-kit/blade-icons, so standard Blade component attribute merging behavior applies. This lets you keep visual styling consistent without hand-editing SVG markup.
- Do I need to publish configuration or run a build step for blade-prime-icons?
- No required publish step or build-tool changes are needed. Installation is handled through Composer with package auto-discovery, which makes it a low-ceremony view-layer dependency. If you plan to use icon caching, confirm that php artisan icons:cache includes this icon set and can be generated at build time before relying on it in CI.
- Is codeat3/blade-prime-icons safe to use in production?
- Technical risk is low because this is a small view-layer package with an MIT license and near-zero code volume, so forking or vendoring is an hours-not-weeks contingency. The main concerns are a single maintainer, low adoption signals, and reliance on the shared blade-ui-kit/blade-icons dependency. If you already use other icon packs, check for Composer constraint conflicts on blade-icons on day one. Also watch for upstream PrimeIcons glyph changes that could silently break template references.
- What is the difference between blade-prime-icons and using the PrimeIcons webfont or CDN?
- The Blade component approach inlines SVG at render time instead of loading an icon webfont through extra CSS or WOFF requests. That avoids render-blocking icon CSS, FOUT, and common icon-font accessibility quirks. The tradeoff is slightly larger HTML payloads and per-icon render cost. It is a good fit for server-rendered admin panels and internal tools, but it is not the right tool for a client-side-only React front end.
- Does codeat3/blade-prime-icons work with Livewire and mail templates?
- Yes, it fits any Blade-rendered Laravel app, including Livewire components and mail templates. It adds nothing to a client-side-only front end, so use it where your icons are rendered server-side through Blade. The simple component syntax keeps icon usage consistent across these views.
- Who maintains codeat3/blade-prime-icons and what is the bus factor?
- The package is maintained by codeat3, a single maintainer operating a large family of near-identical blade-* icon packages. There is consistent release cadence, but no second reviewer, SLA, or commercial backing, and GitHub adoption signals are low. The MIT license and tiny code footprint make in-house patching or vendoring a realistic fallback. Say this explicitly in your decision record rather than treating community-only support as a hidden risk.
- Does the package version track PrimeIcons upstream, and can a minor bump change glyphs?
- Do not assume the package version tracks PrimeIcons upstream; confirm this from release notes and the composer.json history before relying on minor bumps. Icon names and glyphs belong to PrimeIcons and PrimeTek, not to this Blade package. A PrimeIcons major release that renames or retires glyphs can silently break template references. If glyph stability matters, pin versions and review upstream PrimeIcons changes.
Weaver
How can I help you explore Laravel packages today?