Weave Code
Blade Fontisto Icons Laravel Package
codeat3/blade-fontisto-icons
Blade Fontisto Icons provides simple Blade components for the Fontisto icon set, letting you drop scalable SVG icons into any Laravel view with a single tag. Install via Composer, then render icons by name with optional size and styling—no asset pipelines or extra configuration needed.
A package to easily make use of Fontisto Icons in your Laravel Blade views.
Frequently asked questions about Blade Fontisto Icons
- How do I install codeat3/blade-fontisto-icons in a Laravel application?
- Run composer require codeat3/blade-fontisto-icons. Laravel's package auto-discovery registers the service provider, so no manual provider entry or config publishing is needed for baseline use. After that you can drop Fontisto icon components into any Blade view immediately. Installation is trivial; the real work is agreeing on an icon naming convention for your team.
- Which Laravel versions does this Fontisto icon package support?
- The package targets modern Laravel releases, with version 1.6.0 adding Laravel 13 support as a compatibility-only change. If you are on Laravel 11 or 12, that release gives you nothing functionally new, so you can safely defer upgrading. Always check the package's composer.json constraints and confirm the resolved blade-ui-kit/blade-icons version also supports your Laravel line before pinning.
- How do I actually use a Fontisto icon inside a Blade view?
- Render icons with the generated Blade component tag, for example x-fontisto-icon name="home", which outputs an inline SVG. Because the icons are inline SVG, they inherit currentColor and CSS-driven sizing from the surrounding markup. There is no JavaScript, no icon font, and no CDN request involved.
- Do I need to publish configuration or compile assets to use these icons?
- No. The package ships the Fontisto glyphs as individual SVG files and auto-registers them as Blade components, so there is no publish step, no asset pipeline change, and no build required. Everything renders server-side in Blade. That makes it a very small addition to an existing Laravel application.
- How can I change an icon's size, color, or add extra CSS classes?
- Since the output is inline SVG, sizing and color are controlled with normal CSS or utility classes passed through the component, and the icon inherits currentColor from its parent. You can wrap the component in your own element or add classes to control dimensions and hover states. Avoid hardcoding pixel sizes across the app; centralize them in a design token or wrapper component instead.
- Does blade-fontisto-icons work alongside other icon sets using blade-ui-kit/blade-icons?
- Yes. This package is a thin distribution layer on top of blade-ui-kit/blade-icons, so it coexists with other icon-set packages in the same application. Each set registers its own component namespace, which keeps them from colliding. A common approach is wrapping each vendor component behind a single x-icon name abstraction so swapping icon families later is a one-file change.
- Is Laravel package auto-discovery enough, or do I need to register the service provider manually?
- Auto-discovery handles provider registration in standard Laravel applications, so manual registration is unnecessary. You would only register it manually if you have disabled package discovery or are running in an unusual bootstrapping setup. In that case add the provider to your application's provider list.
- Is it safe to use dynamic component names with user input, like x-dynamic-component?
- No. Building a Blade component name from untrusted input, such as concatenating 'fontisto-' with a request parameter, is a component-name injection vector. Only map user input to icons through a server-side allowlist of known glyph names. Keep dynamic icon resolution entirely out of any path that touches request data.
- Are accessibility attributes like aria-hidden and title added automatically?
- No, the vendor components do not inject ARIA attributes, roles, or title elements for you. Consuming markup must supply them based on context: decorative icons should get aria-hidden="true", while meaningful icons need an accessible name via a title element or visually hidden text. Bake this into your own wrapper component so engineers do not have to remember it per usage.
- Does this package affect performance on pages with many icons, and is it maintained?
- Each icon is inlined as a separate SVG, so icon-dense pages will see duplicated markup and a larger HTML payload; measure before rolling it out widely, and consider sprites if volume is high. The package is a single-maintainer, very low-adoption project with reactive maintenance, so treat it as a leaf presentation dependency rather than something core. Also confirm the bundled Fontisto license terms and record any attribution obligations in your third-party notices.
Weaver
How can I help you explore Laravel packages today?