Weave Code
Blade Zondicons Laravel Package
codeat3/blade-zondicons
Blade Zondicons brings the Zondicons icon set to Laravel Blade as simple, self-contained components. Drop icons into any view with a single tag, style them with classes, and skip copying SVG markup by hand.
A package to easily make use of Zondicons in your Laravel Blade views.
Frequently asked questions about Blade Zondicons
- How do I install codeat3/blade-zondicons in a Laravel application?
- Run composer require codeat3/blade-zondicons and Laravel package auto-discovery registers the icon set for you. There is no service provider to add, no config file to publish, and no build step to run. Confirm the PHP and illuminate/* constraints from the tagged composer.json before installing.
- Which Laravel versions does blade-zondicons support?
- The package is a thin wrapper over blade-ui-kit/blade-icons, so it works wherever that dependency and the declared illuminate/* constraints resolve. Version 1.7.0 widened the framework constraints for Laravel 13 compatibility, which means Composer will not refuse to install alongside illuminate/* ^13.0. Check the tagged composer.json in CI rather than relying on changelog wording.
- How do I render a Zondicon inside a Blade view?
- Use the component tag, for example x-zondicon-home with a class attribute, anywhere in a Blade template. The SVG is inlined at render time, so there is no JavaScript or asset pipeline involved. You can drop it into partials, admin screens, or empty states with no extra setup.
- Can I style Zondicons with Tailwind or CSS classes?
- Yes. Classes applied to the component are passed through to the rendered SVG, so Tailwind utilities like w-5 h-5 or text-gray-500 work as expected. That keeps sizing and color consistent with the rest of your Blade views without editing the icon markup.
- Do I need to register a service provider or publish configuration?
- No. Package auto-discovery handles registration and there is no configuration to publish or keep in sync. That is also why integration takes hours rather than days, and why removing it later is a clean composer remove plus swapping in raw SVGs or another icon set.
- How many icons are included in the Zondicons set?
- Reference material for this package and the upstream set cites different figures, commonly 220+ and roughly 290 glyphs. Confirm the actual count from the tagged package before committing to a number in a spec or design handoff. Either way, treat the set as a fixed vocabulary rather than a growing library.
- What happens if an icon name is missing or gets renamed?
- The component renders empty rather than throwing an error, so a dropped or renamed glyph shows up as a visual regression instead of a runtime alert. If icons matter on a key surface, add a smoke test that asserts expected component output. Pin the version and review changelogs before upgrading.
- Can I change the x-zondicon prefix to avoid component name collisions?
- Components are namespaced under a zondicon prefix, which keeps them distinct from your own Blade components. Prefix and set registration come from blade-ui-kit/blade-icons, so if you already have colliding component names, check the blade-icons configuration options in the installed version. Decide on prefixing and icon-set naming before adoption rather than after.
- Is blade-zondicons actively maintained, and what are the alternatives?
- It is a community-maintained package with a small footprint, around 48 stars and no dependents, and changelogs are brief. The Zondicons artwork is effectively frozen upstream, so expect no new glyphs. Alternatives are vendoring the raw SVGs into your repository or consolidating on another blade-icons set such as Heroicons or Eva under one naming convention.
- Do Zondicons work in production and can they be tested without a build step?
- Yes. Icons are server-rendered inline SVG with no JavaScript dependency and no build pipeline, so they render the same locally and in production. The realistic failure mode is cosmetic: a missing or misrendered icon on one surface. Test by asserting that key views render the expected component output instead of relying on visual checks alone.
Weaver
How can I help you explore Laravel packages today?