Weave Code
Blade Simple Icons Laravel Package
codeat3/blade-simple-icons
Laravel Blade components for rendering Simple Icons SVGs with clean syntax. Use brand icons by name in any Blade view, customize size and color, and avoid extra JavaScript or asset pipelines.
A package to easily make use of "Simple Icons" in your Laravel Blade views.
Frequently asked questions about Blade Simple Icons
- How do I install codeat3/blade-simple-icons in a Laravel app?
- Install it with composer require codeat3/blade-simple-icons. There is no service provider to register or config file to publish on the happy path, because the components are picked up by Laravel's Blade component auto-discovery. You then drop the package's component tag for the brand you want into any Blade view and it renders an inline SVG. The first icon can be on screen within minutes of the require finishing.
- Which Laravel and PHP versions does blade-simple-icons support?
- The package is a generated set of Blade components, so it needs a Laravel release that supports Blade component auto-discovery, plus whatever PHP range is declared in its composer.json. Check the constraint on Packagist before adding it to an older application, since it is a presentation-only package with no service provider or runtime bootstrapping of its own. If you are on an unsupported Laravel version, vendoring the SVGs directly is usually simpler than back-porting.
- How do I change the size and color of a Simple Icons Blade icon?
- Attributes you put on the component are passed through to the root svg element, so width, height, and CSS classes all work the way you would expect. The icons use currentColor for fill, which means you control colour with your existing text colour utilities or plain CSS rather than package-specific options. Because sizing and colour come from your host application's styles, Tailwind, plain CSS, and inline styles all behave consistently.
- How do I render an icon when the brand name comes from a database or CMS?
- Blade resolves components by tag name, so a database-driven brand list needs a wrapper rather than a hard-coded tag. Use Laravel's dynamic component resolution with a computed slug, such as mapping a stored brand to the package's component name at render time. Wrap that in your own component that falls back to a generic placeholder when the slug does not resolve, otherwise an unknown name throws a component resolution exception. Most teams also keep a small slug inventory that maps human brand names to icon names.
- Why am I getting a component not found error for an icon that used to work?
- Simple Icons renames and removes marks upstream in response to rebrands and trademark requests, and those changes can land in what looks like a routine composer update. Because the wrapper's major version does not track upstream's, a passing update can silently drop a component and the resulting exception often does not name the offending icon clearly. Treat icon slugs as part of your application's public surface: grep for them, cover them in tests, and always render through a fallback. The reliable inventory of what you actually have is the component directory inside the installed vendor tree, not the version constraint.
- Does blade-simple-icons make external requests or need a CDN, JavaScript, or CSS build step?
- No. Icons are rendered as inline SVG on the server, so there are no CDN calls, no JavaScript, no asset pipeline changes, and no migrations. The one infrastructure detail to check is your Content Security Policy, which must permit inline SVG in the document. The trade-off is page weight: a large grid of brand marks inflates your HTML and costs one view resolution per icon.
- Can I use these icons in Livewire components, Filament or Nova admin panels, and Blade mailables?
- Yes for anything that renders Blade on the server, including Livewire screens, Filament and Nova admin surfaces, and Blade-based notifications. It is a natural fit there because the SVG is inlined with currentColor fill and inherits your existing layout and colour classes. For customer-facing email, be aware that inline SVG support varies by mail client, so a PNG fallback is often safer than shipping the SVG markup.
- Does blade-simple-icons work with Inertia.js or a Vue/React SPA front end?
- It is a poor fit for Inertia or SPA-only rendering, because the icons would have to be serialised as HTML strings and sent across the wire. If your front-end build already tree-shakes an npm icon package, that approach is the better one and this package adds nothing. Use it where Blade owns the markup: monolith views, admin panels, and server-rendered mail.
- Is it legal to use these brand logos in my Laravel application?
- The wrapper code is MIT licensed, but each logo is governed by the brand's own guidelines, so the package cannot grant you usage rights. The breadth of third-party marks is exactly the dimension that carries legal exposure, and upstream removals are often legal-driven rather than technical. Decide who owns per-asset trademark policy and which surfaces, customer-facing versus internal admin, need sign-off before a mark appears. Avoid uses brands restrict, such as implying endorsement, recolouring, or standing in for your own product identity.
- How do I keep the icons updated, and what happens if the package is abandoned?
- Pin the version you have tested and re-run your slug tests whenever you update, rather than assuming a semver bump is safe. The wrapper has very few stars and effectively one maintainer plus a sync bot, so continuity is a real consideration. The mitigating factor is that the artifact is generated from a public dataset, so the exit path is cheap: fork it, or regenerate the Blade components from Simple Icons yourself. If you only need a handful of marks, vendoring those SVGs is simpler than taking on a dependency and its update cadence.
Weaver
How can I help you explore Laravel packages today?