Weave Code
Blade Simple Line Icons Laravel Package
codeat3/blade-simple-line-icons
Blade Simple Line Icons provides a clean set of Blade components for rendering Simple Line Icons in Laravel views. Install the package, then use simple x- or @svg-style tags to drop scalable, styleable icons anywhere in your app without extra markup or config.
A package to easily make use of Simple Line Icons in your Laravel Blade views.
Frequently asked questions about Blade Simple Line Icons
- How do I install codeat3/blade-simple-line-icons in Laravel?
- Run composer require codeat3/blade-simple-line-icons from the root of your Laravel project. Laravel's package auto-discovery registers the service provider, so there is no publish step, no config file to edit, and no migration to run. A working spike takes under an hour, and usually under a minute.
- Which Laravel versions does blade-simple-line-icons support?
- Version 1.6.0 added Laravel 13 compatibility alongside the earlier supported releases, so applications on 10, 11, 12, and 13 are covered. Check the composer.json constraint before pinning, because a future bump may drop older framework versions. If you maintain several Laravel versions, pin the package constraint explicitly and carry it in your upgrade runbook.
- How do I use these icons in a Blade view?
- Use Blade component syntax such as x-simple-line-icons-home and the package renders the matching SVG inline in your view. Because the output is inline SVG, the icon inherits the surrounding text color and can be sized with CSS utilities. No asset pipeline, CDN request, or icon font load is involved.
- Is the correct component prefix x-simple-line-icons or x-simple-line-icon?
- The documentation is inconsistent, showing both x-simple-line-icons-* and x-simple-line-icon-* in different places, which is a reliable signal of low documentation maturity. Confirm the real prefix by rendering one tag in a scratch view or by checking the package source before writing it across your templates. Using the wrong prefix produces a component-not-found exception at render time, not a silently broken icon.
- Do I need to publish configuration or register the service provider manually?
- No. The package is a thin wrapper over blade-ui-kit/blade-icons with no configuration surface, no runtime logic, and no persistence, and auto-discovery handles provider registration. There is nothing to publish and no front-end build step to wire up. That also means the dependency stays confined to the view layer and cannot constrain your domain model, routes, or database.
- Can I change the icon size and color, or add my own CSS classes?
- Yes. Since each icon renders as inline SVG, you can pass classes and attributes through the component tag and style the result with Tailwind or plain CSS. Sizing typically comes from width and height utilities, while color follows currentColor from the parent element. There is no design-token layer, so treat the output as raw artwork rather than a themed design-system primitive.
- Does blade-simple-line-icons work with Livewire, Inertia, and Vue?
- Blade components compile server-side, so they work anywhere Blade renders, including Livewire views and the initial Inertia page response. They do not help inside a pure Vue or React component tree, where you would import the SVG files directly instead. In a mixed stack, keep icon usage in the Blade layer where the components are registered.
- How should I test that the icons render correctly?
- A single smoke test per icon package is enough: render a view containing one icon component and assert the response contains non-empty SVG markup. Because the package has no logic, state, or I/O, there is no meaningful unit surface beyond that check. That same test catches renamed components after a package upgrade, which is the realistic failure mode.
- What are the alternatives to blade-simple-line-icons?
- The realistic alternatives are hand-rolled SVG partials, a general-purpose icon package you may already have installed such as blade-ui-kit/blade-icons with a different icon set, or an icon font loaded from a CDN. This package is the cheapest of those to start with, but the least future-proof to stay on, since the upstream Simple Line Icons artwork is effectively frozen at around 190 monochrome outline glyphs. Use it as a supplementary icon source for admin panels, internal tools, and MVPs, not as the backbone of a governed design system.
- Is the package actively maintained, and what happens if it is abandoned?
- It has a single maintainer and negligible adoption, with the 1.6.0 Laravel 13 compatibility bump being the only recent evidence of attention. That is acceptable for a commodity wrapper with no runtime logic, but it means there is no user community to surface regressions and no downstream pressure keeping it current. Record it in your dependency register as a lifecycle risk and rehearse a fork path, since the source only wraps blade-icons and vendoring it is a few hours of work.
Weaver
How can I help you explore Laravel packages today?