Weave Code
Blade Game Icons Laravel Package
codeat3/blade-game-icons
Blade Game Icons brings game-icons.net SVG icons to Laravel Blade as simple components. Drop ready-to-use icons into your views with clean tag syntax, customize size and color via attributes, and speed up game UI development.
A package to easily make use of Game Icons in your Laravel Blade views.
Frequently asked questions about Blade Game Icons
- How do I install codeat3/blade-game-icons in a Laravel app?
- Install it with composer require codeat3/blade-game-icons. The package supports Laravel package auto-discovery, so you normally do not need to register a service provider manually. There are no mandatory migrations or config files described, and the main follow-up is confirming that blade-icons is available in the host app.
- Do I need blade-ui-kit/blade-icons installed to use Blade Game Icons?
- Yes. Blade Game Icons is a thin icon-set provider over blade-ui-kit/blade-icons, not a standalone renderer, so the host Laravel app must already run blade-icons or adopt it. It composes alongside other blade-icons sets such as Heroicons or Font Awesome, but plan a shared component prefix so names do not collide.
- Which Laravel versions and blade-icons versions does this package support?
- The package is intended for Laravel Blade applications, but the supplied context does not list the exact Laravel or blade-icons constraints for each release. Check the composer.json for the version you plan to install and verify the Laravel 13 claim across the full support matrix. Treat blade-icons major compatibility as part of your framework-upgrade review.
- How do I render a Game Icon in a Laravel Blade view?
- Render an icon as a Blade component, for example <x-game-icons-sword /> as shown in the overview. Components are auto-registered with kebab-case names, so the icon name maps to the tag you use in the view. Attribute passthrough lets you add class, width, height, and other presentation attributes directly on the component.
- How do I change the size, color, or CSS classes of a Game Icon?
- Pass presentation attributes directly through the component, such as class, width, and height. For example, set a Tailwind-style class to control color and sizing, or use width and height attributes for explicit dimensions. The package does not require a build step, so the SVG output is the final view markup.
- Does Blade Game Icons require JavaScript or a build step?
- No. Blade Game Icons outputs pure SVG through Blade components, with no JavaScript and no build step required. It works in any view layer where Blade renders, including Livewire views and Inertia server-rendered Blade shells. For a pure API service or a JavaScript SPA, using SVGs directly in the asset pipeline is usually simpler.
- How should I test Blade Game Icons components?
- The context does not describe dedicated testing helpers, so test it as you would any Blade component. Render a view that uses the component in a Laravel test and assert that the expected SVG output appears, while ensuring blade-icons is registered during test bootstrap. CI should actually render at least one component, not only install the Composer package.
- How much does the SVG icon set affect Composer install, CI, and deploy size?
- The Game Icons catalogue contains several thousand SVGs, so the main production concern is artifact size rather than runtime rendering. Measure Composer install time, cold deploy time, and container image size before rollout instead of assuming the impact is negligible. The SVGs are static assets, so they should be tracked in deploy and CI capacity planning.
- What attribution is required for Game Icons, and who owns license compliance?
- Game Icons artwork is CC BY 3.0 and requires attribution. The package cannot place that attribution in your UI for you, so the adopting team must give it a real home such as an about page, credits screen, or legal page. Treat license compliance as a release-gate item and verify the catalogue terms against the upstream Game Icons project.
- Is codeat3/blade-game-icons actively maintained, and what are the alternatives if it stalls?
- It is a single-maintainer package with low commit volume and few dependents, so treat it as a low-to-moderate supply-chain risk. Do not make it a blocker for a Laravel or blade-icons major upgrade; if upstream stalls, vendor the SVG files and fork the assets rather than the roadmap. Alternatives include using other blade-icons sets, importing Game Icons SVGs into your own asset pipeline, or rendering icons directly in a front-end build.
Weaver
How can I help you explore Laravel packages today?