Weave Code
Blade Humbleicons Laravel Package
codeat3/blade-humbleicons
A Laravel Blade component package that brings the Humbleicons icon set directly into your views. Render any icon with a simple x-humbleicon tag, adjust size and other attributes inline, and avoid copying raw SVG markup into your templates.
A package to easily make use of "Humbleicons" in your Laravel Blade views.
Frequently asked questions about Blade Humbleicons
- Can I install codeat3/blade-humbleicons with Composer?
- Yes. Run composer require codeat3/blade-humbleicons in your Laravel project and let package auto-discovery register the Blade components. There is no config file to publish, no assets to compile, and no environment variable to set. After install you can use the components immediately in any Blade view.
- How do I render a Humbleicons icon in a Laravel Blade view?
- Use the x-humbleicons-name tag, replacing name with the icon handle, for example <x-humbleicons-home />. The package expands the tag to inline SVG at render time, so you do not copy SVG markup into templates. You can pass class and other attributes through the tag.
- How can I change an icon's size, color, or stroke width?
- Pass Tailwind or CSS classes via the class attribute, such as <x-humbleicons-home class='w-6 h-6 text-blue-600' />. Because output is inline SVG, color, sizing, and stroke can also be controlled with CSS rules. Attribute passthrough lets you add aria labels or other markup attributes.
- Does blade-humbleicons support Laravel 13?
- Release 1.2.0 was a single-change update for Laravel 13 compatibility, so the wrapper has been widened for that major. The real constraint is in the published composer.json, including the illuminate/support range and any blade-icons dependency. Check that it resolves against your current composer.lock before adopting.
- Does this package work in an API-only or Inertia/Vue/React application?
- It is a view-layer-only Blade package, so it does nothing in an API-only service where Blade never renders. The same applies to Inertia or React/Vue surfaces that do not use Blade components; use the Humbleicons SVG set directly there. Only adopt it if your team renders Blade views.
- What dependencies does codeat3/blade-humbleicons pull in?
- The package is expected to depend on a Blade icons foundation such as blade-ui-kit/blade-icons and illuminate/support, but the authoritative answer is the published composer.json. That transitive range, not the wrapper changelog, is the true Laravel compatibility surface. Read it before adding the package to a dependency register.
- Is blade-humbleicons safe and performant in production?
- It has a low-risk architecture: components expand to inline SVG through cached-compiled Blade, with no database, queue, HTTP, or service provider side effects beyond component registration. The caveats are provenance, since the package has zero stars and zero dependents, and upstream icon-set liveness. Pin the version, smoke-test rendering, and avoid treating it as tier-one infrastructure.
- How are new Humbleicons icons added, and how often is the package updated?
- The package ships the icon set, so new glyphs arrive through package releases from the wrapper maintainer rather than being fetched at runtime. Maintenance is reactive and event-driven; release 1.2.0 only added Laravel 13 compatibility. Existing icons keep rendering if upstream stalls, but you should watch updates with dependency automation.
- What are alternatives to blade-humbleicons for Laravel Blade icons?
- Alternatives include blade-ui-kit/blade-icons with other icon sets, blade-heroicons, blade-fontawesome, or copying SVGs into your own Blade components. The trade-off is setup effort versus control: wrappers are convenient, while a local component gives you full ownership. Choose based on icon style, license, maintenance activity, and whether you need many sets.
- What license does blade-humbleicons use, and can I use it commercially?
- The wrapper is stated as MIT, but the Humbleicons icon set carries its own license that must also be checked. Commercial product UI use and redistribution inside a shipped application depend on both licenses being permissive. Confirm the asset license in the repository before shipping.
Weaver
How can I help you explore Laravel packages today?