Weave Code
Blade Gala Icons Laravel Package
codeat3/blade-gala-icons
A Blade component package that brings the Gala icon set to Laravel. Render any Gala icon in your Blade views with a simple, expressive tag, keeping SVG markup clean and consistent while adding crisp icons to your UI with minimal effort.
A package to easily make use of Gala Icons in your Laravel Blade views.
Frequently asked questions about Blade Gala Icons
- How do I install codeat3/blade-gala-icons in a Laravel app?
- Install it with Composer by running composer require codeat3/blade-gala-icons. The package is auto-discovered through Laravel package discovery, so you do not need to register a service provider manually. Once installed, the Gala components are immediately available in your Blade views under the gala prefix.
- Which Laravel and PHP versions does blade-gala-icons support?
- The package targets PHP 8.x and modern Laravel releases, and version 1.4.0 widened the framework constraints to include Laravel 13. That release is compatibility-only, with no new icons or API changes. Because no CI matrix is visible in the repository, confirm the exact floors against your locked versions using composer why-not before upgrading.
- How do I use a Gala icon in a Blade template?
- Drop the component tag into any Blade view, for example <x-gala-heart />, and the package inlines the matching SVG at render time. No external asset request, sprite sheet, or JavaScript is involved, so the icon is cacheable and styleable with CSS. The tag name maps directly to the icon name in kebab-case.
- Can I set size, color, and CSS classes on a Gala icon component?
- Yes. The component accepts attributes such as size, color, and class, which are passed through to the rendered SVG element. You can also style the inline SVG with your own CSS, including currentColor for theme-aware coloring. This keeps icon markup consistent while still letting Tailwind or hand-written styles control appearance.
- Do I need to publish the blade-gala-icons config file?
- No. The package is zero-configuration and works as soon as Composer finishes installing it. Publishing the config is optional and only useful if you want to change the component prefix or override default attributes. Most applications never need to touch it.
- How do I find the correct icon name or component name for a Gala icon?
- Component names follow the Gala SVG file names converted to kebab-case, so <x-gala-arrow-right /> corresponds to the arrow-right icon. Browse the icons directory in the repository or the upstream Gala set to confirm the exact name. Gala is a comparatively small catalogue, so check coverage against your existing icon inventory before standardising on it.
- What happens if a Gala icon name does not exist — does it throw an error?
- An unresolved icon name typically renders blank output rather than throwing an exception, so a typo can ship to production with no error signal. Because there is no runtime failure, a normal feature test will not catch it either. Add a smoke test that asserts the rendered HTML contains an svg element for each icon you rely on.
- Does blade-gala-icons work with Livewire, Inertia, Vue, or React?
- It works anywhere Blade renders, including Livewire components and standard server-rendered pages. It is not a good fit for SPA or Inertia frontends that already bundle icons through Vite, since that creates a second icon pipeline with no consolidation benefit. API-only services have no use for it at all.
- How does blade-gala-icons compare to Heroicons or other Blade icon packages?
- It is built on blade-ui-kit/blade-icons, the same foundation used by many Blade icon packages, and simply registers the Gala catalogue as a component namespace. Heroicons, Tabler, and similar sets have deeper catalogues, so choose based on actual icon coverage rather than package features. It can coexist with an existing blade-icons install by adding a namespace rather than a second runtime dependency.
- Is blade-gala-icons actively maintained, and what license applies to the Gala SVGs?
- The package is MIT licensed, but the bundled Gala SVGs carry their own upstream terms that your application inherits, so verify whether attribution in a NOTICE file or UI is required before shipping. Maintenance is present but reactive: a single maintainer, low pull-request throughput, and a 1.4.0 release that only widened framework constraints. For static SVG assets that is usually tolerable, but keep a vendoring fallback documented if icons become business-critical.
Weaver
How can I help you explore Laravel packages today?