Weave Code
Blade Rpg Awesome Icons Laravel Package
codeat3/blade-rpg-awesome-icons
Blade RPG Awesome Icons provides a simple Blade component for rendering RPG Awesome icons in your Laravel views. Install the package, use the x-rpg-awesome component with an icon name, and get scalable SVG icons for fantasy and RPG-themed interfaces with minimal markup.
A package to easily make use of "RPG Awesome Icons" in your Laravel Blade views.
Frequently asked questions about Blade Rpg Awesome Icons
- How do I install codeat3/blade-rpg-awesome-icons in a Laravel app?
- Run composer require codeat3/blade-rpg-awesome-icons and the package registers itself through Laravel package auto-discovery. There is no publish step, no npm install, no font hosting, and no config file to edit. Most teams get a first rendered glyph within the hour, and most of that time goes into picking icon names rather than integrating.
- Which Laravel and PHP versions does blade-rpg-awesome-icons support?
- Release 1.7.0 is a constraint-only update that declares compatibility with Laravel 13 alongside the earlier supported majors, with no feature or breaking changes. Because it builds on blade-ui-kit/blade-icons, the effective PHP and Laravel floor is set by that underlying package, so check composer.json in your lock file before adopting on an older application. Confirm whether the widened constraint was actually exercised in CI rather than treat "declared compatible" as "tested".
- How do I use the RPG Awesome icon component in a Blade view?
- Each icon is exposed as a Blade component named after the glyph, so you write something like <x-rpg-awesome-swords /> directly in your template. The package maps icon names from the RPG Awesome set, so the name you pass corresponds to a glyph in that artwork library. The output is inline SVG rendered at compile time, which means it scales cleanly and inherits your page styling.
- Does blade-rpg-awesome-icons publish any config, assets, or migrations?
- No. The package is a thin wrapper that registers the RPG Awesome glyph set with blade-ui-kit/blade-icons and exposes it as Blade components. There is no configuration file, no published assets, no routes, no migrations, and no queue or credential surface. That makes it a leaf-level presentation dependency with a very small blast radius.
- Should I use this package or the RPG Awesome CSS webfont with <i> tags?
- The package renders inline SVG at compile time, so there is no font file to host and no font-src exception needed in your Content Security Policy. The traditional approach uses markup like <i class="ra ra-swords"></i> plus the vendored CSS and icon font from RPG Awesome. Both render equivalent glyphs and can coexist indefinitely, so you can convert templates opportunistically on your normal change cadence.
- Can I use blade-rpg-awesome-icons with Inertia, React, Vue, or an API-only service?
- No. This is a Blade-only wrapper, so it fits wherever Blade is your rendering layer and does nothing for Inertia, React, Vue, native clients, or API-only services. In those cases consume the upstream RPG Awesome SVG set directly instead of pulling in a Laravel-shaped dependency. The real adoption question is whether you have a themed, Blade-rendered surface that justifies the dependency.
- How do I test that an RPG Awesome icon renders in my Blade view?
- Render the view or component in a feature test and assert the SVG markup appears, for example with assertSee or assertSeeHtml against a distinctive path or class from the glyph. There is no database, network, or filesystem interaction involved, so the tests stay fast and deterministic. If you need stricter guarantees, snapshot the rendered SVG of the handful of icons your UI actually relies on.
- Is blade-rpg-awesome-icons safe to use in production?
- Yes. It carries no persistence, routing, migrations, queue workers, or credentials, and it changes only what a template emits. The main production concerns are yours to manage: inline SVG adds page weight, so budget for the number of glyphs on a page, and treat accessibility as your responsibility since the wrapper supplies a component name and class, not semantics. Never let business logic depend on an icon rendering.
- Is the package actively maintained, and will new icons be added?
- RPG Awesome is effectively a finished artwork set, so expect a frozen icon inventory from day one and design your UI vocabulary around that. The package has a single maintainer, which is a real but limited risk because the wrapper is thin: vendoring the SVGs you use is an hours-scale exit rather than a re-platforming. Record the icon vocabulary constraint in your dependency register at adoption so cosmetic drift is a conscious decision.
- What are the alternatives to blade-rpg-awesome-icons?
- If you only need two or three decorative glyphs, inline the SVG markup directly and skip the dependency entirely. Otherwise you can register the RPG Awesome set yourself through blade-ui-kit/blade-icons, use a different icon package such as blade-heroicons or blade-fontawesome, or keep the vendored RPG Awesome CSS webfont. Verify the upstream artwork license, which is separate from the package's MIT license, before distributing the icons in your product.
Weaver
How can I help you explore Laravel packages today?