Weave Code
Blade Radix Icons Laravel Package
codeat3/blade-radix-icons
A Laravel Blade package for rendering Radix Icons as simple, customizable components. Use convenient x-radix-icon tags in your views, with support for sizing, colors, and easy Composer installation.
A package to easily make use of "Radix Icons" in your Laravel Blade views.
Frequently asked questions about Blade Radix Icons
- How do I install codeat3/blade-radix-icons in Laravel?
- Run composer require codeat3/blade-radix-icons and the service provider is auto-discovered, so there is nothing to register by hand. No config file needs to be published and no npm or asset build step is involved. Once Composer finishes, every bundled icon is immediately available in your Blade views as an x-radix component.
- Which Laravel versions does blade-radix-icons support?
- Release 1.9.0 updated the constraint to declare Laravel 13 compatibility alongside earlier supported versions. Because the package is a thin wrapper over blade-ui-kit/blade-icons, Laravel 13 only resolves cleanly if that upstream dependency and your PHP floor also satisfy it. Confirm in your composer.lock that blade-icons resolved as expected, and remember that declared support is not the same as an exercised test matrix.
- How do I use a Radix icon in a Blade template?
- Use the component tag that matches the icon name, for example x-radix-home or x-radix-arrow-right, which renders an inline SVG. Component names follow the icon names from the Radix set, so browse the packaged list to find the exact one you need. No controller, view data, or build step is required because each component is self-contained.
- How do I change the size and color of a Radix icon?
- Pass attributes or classes directly on the tag, such as class with Tailwind width, height, and text color utilities, which the component forwards to the SVG. Because the output is a plain inline SVG, utilities for sizing, fill, and stroke work exactly as they do on hand-written markup. This keeps icons themed consistently with the rest of your design system without extra CSS.
- Do I need to publish config or enable icon caching for performance?
- There is no configuration surface in this package itself, since it only registers the Radix set with blade-ui-kit/blade-icons. If you want sprite or caching mode for icon-dense pages, publish the blade-icons config file and enable it there rather than forking this package. For typical admin panels and marketing pages, direct inline SVG output is perfectly adequate.
- Does blade-radix-icons require JavaScript or an npm build?
- No. The package emits inline SVG from PHP, so there is no JavaScript runtime, no npm dependency, and no asset compilation to wire into your pipeline. That makes it a clean fit for server-rendered Blade applications where you want icons without touching the frontend toolchain.
- How many icons are included in blade-radix-icons and what license applies?
- Over 300 Radix icons ship as individual components drawn on a consistent 15x15 grid. The Radix Icons set is MIT licensed, and the package is a Blade wrapper around those assets, so redistribution and vendoring are straightforward. Verify the bundled set matches your design system before standardising on it.
- Can I use blade-radix-icons alongside Heroicons or other Blade icon packs?
- Yes. Each blade-icons set registers its own component prefix, so x-radix components coexist with x-heroicon and similar tags in the same application. Keep names distinct in your views and avoid wrapping two sets inside one ad-hoc abstraction, which is where naming collisions usually appear.
- What happens if I reference a Radix icon name that does not exist?
- Unknown or renamed components typically render empty markup rather than throwing an exception, so the defect surfaces in visual QA instead of CI. Add a smoke test or a rendered-output assertion for the icons your UI actually depends on, and pin the package version so an upstream rename cannot silently break a page.
- What are the alternatives to blade-radix-icons and how hard is it to migrate away?
- The main alternatives are using blade-ui-kit/blade-icons directly with your own SVG set, or vendoring the MIT-licensed Radix SVGs into resources and keeping the same component names. Because this is a presentation-only wrapper with no runtime services, data, or migrations, exit is mechanical, though the single-maintainer bus factor means you should record that fallback decision up front. If you also run an Inertia, React, or Vue frontend with an existing JS icon pipeline, prefer one icon path rather than mixing both.
Weaver
How can I help you explore Laravel packages today?