Weave Code
Blade Line Awesome Icons Laravel Package
codeat3/blade-line-awesome-icons
Blade components for Line Awesome icons in Laravel. Drop <x-line-awesome-* /> tags into your views to render any icon as clean inline SVG, with no JavaScript or extra config. Publishable assets and simple customization make it easy to use across any Blade app.
A package to easily make use of Line Awesome Icons in your Laravel Blade views.
Frequently asked questions about Blade Line Awesome Icons
- How do I install codeat3/blade-line-awesome-icons in a Laravel app?
- Install it with composer require codeat3/blade-line-awesome-icons. Laravel package auto-discovery registers the service provider automatically. You can optionally publish config or assets with vendor:publish if you need to customize them. No npm, Vite, or manual provider registration is required.
- Which Laravel versions does blade-line-awesome-icons support?
- Version 1.6.0 adds Laravel 13 compatibility, and the README states Laravel 8+. Before upgrading, inspect the composer.json constraint diff to confirm whether the supported range was widened to include both 12 and 13 or the minimum was raised. Also confirm your PHP floor and the transitive blade-ui-kit/blade-icons version pair.
- How do I use Line Awesome icons in Laravel Blade views?
- Use the Blade component syntax directly in your views, for example <x-line-awesome-user />. The package resolves the matching Line Awesome SVG and renders it as clean inline SVG. There is no JavaScript, webfont link, or extra configuration needed.
- Do I need Node, Vite, or a webfont to use this package?
- No. There is no Node, Vite, Mix, or webfont step. Icons ship as static SVG files and are rendered inline through Blade components. That keeps deployment simple, though icon-dense pages benefit from running the icon cache command.
- How do I cache icons for production performance?
- Run php artisan icons:cache during deployment to collapse per-icon filesystem lookups into a manifest read. Treat it as a required deploy step for icon-dense pages such as nav bars and data tables. Verify it works in your topology, especially multi-node, read-only filesystem, and container image builds.
- How do I customize icon size, class, and other SVG attributes?
- Pass standard attributes such as class, width, height, and aria attributes directly on the component tag. The package also supports publishing assets and config for deeper customization. Check the rendered SVG output against your known-good blade-ui-kit/blade-icons version pair if you rely on attribute passthrough.
- How should I handle accessibility for decorative and semantic icons?
- Inline SVGs do not get accessible names by default, so define a call-site convention. Mark decorative icons with aria-hidden='true', and give meaningful icons role='img' plus a title or aria-label. Without that convention you can ship an accessibility regression compared with webfont text alternatives.
- How do I test Blade views that render Line Awesome icon components?
- Because output is inline SVG, you can render the Blade view in a feature or view test and assert the expected icon markup appears. No asset compilation or HTTP call is involved, so tests remain fast. Include an accessibility assertion for meaningful icons if that matters to your UI.
- Is codeat3/blade-line-awesome-icons safe for production and actively maintained?
- This package is MIT-licensed with a single maintainer and community-grade support, so pin exact versions and commit the lockfile. It compares favorably to a Font Awesome webfont for render control and to wiring blade-ui-kit/blade-icons manually, but it depends on that package for rendering behavior. Line Awesome itself is effectively frozen, so treat new glyph coverage as unlikely and record whether this is permanent or interim.
- How do I migrate existing la la-* webfont icons to these Blade components?
- Find every i class='la la-*' or webfont call site across Blade views, mail templates, and PDF or report renderers. Build a name-mapping table and replace each with the matching <x-line-awesome-* /> component. Finish with a visual-regression pass, and size the sweep before committing to a date because the conversion work, not the dependency, is the schedule risk.
Weaver
How can I help you explore Laravel packages today?