Weave Code
Blade Laravel Package
solar-icons/blade
solar-icons/blade provides Laravel Blade components for rendering Solar icon sets, making it easy to drop scalable SVG icons into your views with simple, expressive tags and minimal setup.
Solar Icons for Laravel Blade
Frequently asked questions about Blade
- How do I install solar-icons/blade in a Laravel application?
- Run composer require solar-icons/blade; the service provider is auto-discovered and registers the Solar icon set as Blade components plus an svg() helper. You can optionally run vendor:publish to copy the package config and, if you need them, the raw SVG assets. After that you can drop icons into any Blade view with an x-solar tag.
- How do I change the stroke width for every Solar icon at once?
- Publish the package config and set the single stroke-width value there; Blade Icons applies it at render time rather than relying on markup baked into each SVG file. That gives you one source of truth instead of duplicating the attribute across assets. Confirm the configured value matches the stroke weight your app rendered before the upgrade.
- Why do my Solar icons look thinner after upgrading to v2.0.1?
- In v2.0.1 the stroke width is applied from package config at render time, and the published raw SVG assets deliberately ship without a baked stroke-width attribute. Any asset rendered standalone therefore falls back to the SVG default of 1, which looks thinner than v2.0.0 output. Nothing throws an error; the change is purely visual, so a visual diff on an icon-heavy page is the fastest way to catch it.
- My stroke-width override on an icon is being ignored. What changed?
- Earlier versions produced a duplicate stroke-width attribute whenever you overrode the width on a static component or through the svg() helper, and browsers honor the first occurrence, so the override was silently dropped. v2.0.1 resolves the attribute once at render time, which removes the duplicate and makes overrides take effect. If an override still seems ignored, check whether your published config value is now the only thing controlling stroke weight.
- Can I use the published Solar SVG assets outside Blade components?
- Yes, you can publish the raw SVGs and use them anywhere, but treat that as a separate integration with its own styling contract. The published files intentionally have no stroke-width, so set it downstream with a CSS rule or a presentation attribute on the wrapping element or svg. This is the path to use for email templates, img tags, CDN-served sprites, or Figma handoffs.
- Does solar-icons/blade work with Livewire and Inertia?
- Yes. The package emits inline SVG through Blade components, so it slots into Blade views, Livewire components, Inertia SSR output, and mail templates without touching your build pipeline. There is no JavaScript dependency and no client-side runtime required. Teams rendering icons in outbound email should use the published-asset path and set stroke width explicitly.
- Which Laravel and blade-ui-kit/blade-icons versions does this package support?
- The package follows the standard Laravel service-provider and Blade component registration pattern and does not couple tightly to a specific framework version. Its meaningful constraint is blade-ui-kit/blade-icons, which must be new enough to support the config-driven stroke-width resolution introduced in v2.0.1. Check the composer.json constraints of both packages before upgrading on older Laravel releases.
- Does solar-icons/blade require npm or an asset compilation step?
- No. Icons render as inline SVG from Blade components, so there is no npm install, bundler config, or compiled CSS to maintain. You only need a build step if you choose to consume the published raw SVG files through your own front-end pipeline. Composer require plus an optional vendor:publish is the whole setup.
- How should I test the upgrade to v2.0.1 before shipping it?
- Diff your published config against the package config to catch overrides that would now be the only thing controlling stroke weight, then run a visual regression pass on a page that uses many icons. Inspect the rendered markup to confirm each svg carries a single stroke-width attribute. If you publish raw assets, decide explicitly between re-publishing and setting stroke width downstream in CSS before promoting the change.
- What are the alternatives to solar-icons/blade?
- The closest alternative is blade-ui-kit/blade-icons with a different icon set, which uses the same component registration model and the same svg() helper conventions. Other common options are dedicated icon-set packages such as Blade Heroicons or building your own Blade component around a directory of SVGs. solar-icons/blade is worth choosing when you specifically want the Solar icon family with centralized stroke styling and no JS dependency.
Weaver
How can I help you explore Laravel packages today?