Weave Code
Blade Carbon Icons Laravel Package
codeat3/blade-carbon-icons
Blade Carbon Icons brings IBM's Carbon icon set straight to Laravel Blade. Lightweight components let you render any icon with a simple tag — no SVG copying or extra setup required. Just install, configure, and drop crisp, consistent icons into your views and UI components.
A package to easily make use of Carbon Icons in your Laravel Blade views.
Frequently asked questions about Blade Carbon Icons
- How do I install codeat3/blade-carbon-icons in a Laravel app?
- Run composer require codeat3/blade-carbon-icons in your Laravel project. The package uses Composer autodiscovery, so its service provider registers the <x-carbon-...> Blade components without config publishing, migrations, routes, or extra setup. After that you can render any packaged icon directly in a Blade template.
- Which Laravel and PHP versions does blade-carbon-icons support?
- Version 2.39.0 adds Laravel 13 compatibility, and earlier releases target prior Laravel versions. The release notes do not state a PHP floor, so check the package composer.json constraints and confirm it installs cleanly on each target app without --ignore-platform-reqs. If no app is on Laravel 13 yet, the bump is effectively a no-op and can ride an existing framework upgrade.
- How do I find the right Carbon icon name for a Blade component?
- Component names correspond to icons in IBM's Carbon Design System catalogue, and the package ships hundreds of official glyphs. Confirm each icon you plan to use exists in the Carbon catalogue before swapping templates, because a missing name fails at render time. During migration, inventory current inline SVGs and font icons and map them one-for-one.
- How do I change icon size, color, and CSS classes in Blade Carbon Icons?
- The <x-carbon-icon-name /> syntax accepts attributes for size, color, and CSS classes, so you can style icons inline or with utility classes. There is no enforced house convention, so agree on defaults early or each feature team will reinvent sizing and color rules. Many teams wrap the component in their own Blade partial to standardize those choices.
- Does blade-carbon-icons work with Livewire and Tailwind CSS?
- Yes. Icons are inline SVG rendered by Blade, so they work in standard Blade views, Livewire components, and Tailwind-styled markup. They do not help Inertia, React, or Vue front ends that never render Blade, or API-only services. For those, let the bundler own icon assets instead.
- Does blade-carbon-icons need a build step, CDN, or JavaScript?
- No. The package renders inline SVG at render time with zero JavaScript, no CDN request, and no asset build step. That makes it suitable for strict CSP environments, air-gapped or on-prem deployments, and email or PDF rendering. The trade-off is SVG markup in your HTML output rather than an external sprite.
- How do I make Carbon icons accessible in Laravel Blade?
- The package does not impose accessibility rules; you control attributes on each component. Mark decorative icons with aria-hidden set to true and give meaningful icons a title or role plus an accessible label. Set a house convention early so accessibility does not vary feature by feature.
- Will registering hundreds of Blade icon components slow down my app?
- The full Carbon set is registered as Blade components, so the main cost is view compilation rather than runtime logic. Measure view-cache compile time on a cold deploy instead of assuming it is negligible. Rendering itself is inline SVG with no database, queue, or persisted state, so steady-state overhead is minimal.
- Can I use blade-carbon-icons alongside Heroicons or Font Awesome, and what are the alternatives?
- Running blade-carbon-icons alongside Heroicons, Blade UI Kit, or Font Awesome buys nothing and doubles icon governance. Pick one canonical set and document it. If you only need under about 20 glyphs, an internal SVG partial is cheaper than a dependency; otherwise swap to a sibling blade-* package or vendor the SVGs as your exit path.
- Is blade-carbon-icons actively maintained, and what is its license?
- Expect a community-supported, single-maintainer package with a small dependent base, so treat it as a commodity dependency with a documented exit. The package is MIT licensed, while the upstream Carbon assets are Apache-2.0, so confirm attribution obligations with legal. Keep the version pinned and the replacement plan written down.
Weaver
How can I help you explore Laravel packages today?