Weave Code
Blade Vaadin Icons Laravel Package
codeat3/blade-vaadin-icons
Blade Vaadin Icons offers a lightweight Blade component for embedding Vaadin icons in Laravel apps. Install via Composer and render any icon by name with a simple tag, keeping markup clean and consistent across views, dashboards, buttons, and navigation.
A package to easily make use of "Vaadin Icons" in your Laravel Blade views.
Frequently asked questions about Blade Vaadin Icons
- How do I install codeat3/blade-vaadin-icons in Laravel?
- Run composer require codeat3/blade-vaadin-icons in your Laravel project. Laravel package discovery registers the service provider automatically, so you normally do not need to edit config/app.php. After installation, the Vaadin icon Blade components are available in your views.
- Which Laravel versions does codeat3/blade-vaadin-icons support?
- The 1.7.0 release is described as a Laravel 13 compatibility update, and releases mainly track upstream Laravel support. Check the package composer.json constraint for the exact Laravel versions allowed before upgrading. If 1.7.0 only widens the constraint, it is effectively a no-op; if it drops older versions, coordinate that with your Laravel upgrade.
- How do I render a Vaadin icon in a Blade template?
- Use a Blade component such as <x-vaadin-icon-ab-testing /> for the Vaadin icon whose SVG file is ab-testing.svg. Icon filenames normalise to the component suffix, so the on-disk resources/svg directory in the vendor package is the authoritative inventory. Confirm exact names against that directory rather than guessing from Vaadin website labels.
- Can I style Vaadin icons with CSS classes and dimensions?
- Yes. The components render inline SVG, so you can pass standard HTML and SVG attributes such as class, width, height, and aria attributes. Style them with your existing CSS, including color and sizing rules, without loading icon fonts or JavaScript. Keep dimensions explicit where layout stability matters.
- Are the Vaadin icons accessible for screen readers?
- Treat icons as decorative or meaningful depending on context. For decorative icons, add aria-hidden="true"; for meaningful icons, provide an accessible name with aria-label or an SVG title and appropriate role. Because the output is inline SVG, these attributes can be applied directly in Blade. Test critical flows with a screen reader or accessibility audit.
- How do I test Blade components from codeat3/blade-vaadin-icons?
- Render the Blade view or component in a Laravel test and assert that the expected SVG markup or icon identifier appears. No external service, queue, or JavaScript runtime needs mocking because the package is a presentation-layer binding. Include a few key icons in smoke tests so a broken or renamed component is caught before release.
- Is codeat3/blade-vaadin-icons suitable for production?
- It is lightweight static inline SVG with no icon font or JavaScript runtime, so production risk is low. Cache compiled Blade views as usual and avoid rendering large icon lists unnecessarily. The main operational gap is observability: a missing or wrong icon appears as blank or incorrect HTML rather than a logged exception, so test critical icons.
- Does codeat3/blade-vaadin-icons work with Livewire or Inertia?
- It fits any Laravel app that renders Blade templates, including server-rendered views, Livewire components, and Inertia pages with Blade roots. It is a poor fit for API-only services or heavily client-rendered SPAs where icons belong in the npm build with tree-shaking. Confirm that your consuming surface actually renders Blade before adopting it.
- What are alternatives to codeat3/blade-vaadin-icons?
- You can use blade-ui-kit/blade-icons directly with another icon set, or choose other Blade icon packages such as Heroicons or Font Awesome bindings. For client-rendered SPAs, npm icon libraries with tree-shaking are usually the better fit. Compare icon style, coverage, maintenance, and licensing against Vaadin's line-based vocabulary.
- How risky is depending on codeat3/blade-vaadin-icons long term?
- It has a single maintainer and a small dependency footprint, so the main risk is abandonment rather than runtime failure. The SVGs are static and can be vendored into your app if the package goes stale, so document that fallback. Blade component names are global and prefixed with vaadin-icon, which reduces but does not eliminate collisions with in-house components; detect conflicts by rendering key icons in tests.
Weaver
How can I help you explore Laravel packages today?