Weave Code
Blade Cryptocurrency Icons Laravel Package
codeat3/blade-cryptocurrency-icons
Blade Cryptocurrency Icons gives Laravel developers a simple Blade component for rendering crisp SVG icons for Bitcoin, Ethereum, and hundreds of other coins. Just drop the component into your views with a symbol name—no asset publishing or manual icon management required.
A package to easily make use of Cryptocurrency Icons in your Laravel Blade views.
Frequently asked questions about Blade Cryptocurrency Icons
- How do I install codeat3/blade-cryptocurrency-icons in Laravel?
- Install it with Composer using composer require codeat3/blade-cryptocurrency-icons. Laravel package discovery registers the BladeIcons registrar automatically, so there is no service provider to add and no config file to publish. A single Composer require is the whole setup.
- How do I render a Bitcoin or Ethereum icon in a Blade view?
- Use the Blade component with a symbol name, for example <x-cryptocurrency-icon-btc class="w-8 h-8" /> for Bitcoin or the equivalent name for Ethereum and other supported coins. The component renders an inline SVG directly in your view. No asset publishing or manual icon management is required.
- Which Laravel versions does this package support?
- Laravel 13 support was added in version 1.9.0 as a discrete pull request, which suggests compatibility is validated on demand rather than through a continuously running CI matrix. Check the released composer.json to see whether the constraint is additive across older Laravel majors or narrowed older support. That detail decides whether the upgrade is safe for the Laravel version you actually run.
- Do I need to publish SVG assets or run npm to use these icons?
- No. The package renders icons through the blade-ui-kit/blade-icons registrar, so there is no npm build step, no mandatory asset publish, and no service provider wiring beyond package discovery. Publishing the full set to public/ is optional and mainly adds payload weight compared with consuming icons per component.
- How do I size and color the cryptocurrency icons?
- The SVGs are inline and inherit currentColor, so you can size them with utility classes such as w-8 h-8 and set color with text-* classes. Light and dark theming then come for free from your existing Tailwind or CSS setup. No per-theme icon assets are needed.
- What happens if a newly listed coin has no icon in the set?
- The icon set is a frozen snapshot of a market that lists and rebrands assets weekly, so a newly listed token will have no mark until it is added. Delisted or rebranded assets can render stale marks, and this will not show up in composer audit. Agree a contribution or fork process for adding SVGs and set stakeholder expectations for a missing-icon backlog.
- Does it conflict with other blade-* icon packages or blade-ui-kit/blade-icons?
- Composer resolves a single version of blade-ui-kit/blade-icons across every installed blade-* icon package, so a lagging constraint in any one of them can block an upgrade. Check which BladeIcons major this release requires and compare it with the blade-* packages already in your estate. The transitive pin, not Laravel itself, is the realistic blocker on platform upgrades.
- Is this package safe to use in production given it is single-maintainer?
- Overall technical risk is low because this is a presentation-layer leaf dependency with no service, datastore, queue, network call, or credentials; a failure paints a broken logo rather than breaking a request. The main concern is maintainer concentration: it is effectively single-maintainer with event-driven releases, so pin the version and write down a fork plan, which is essentially copying an SVG directory and a registrar class. Also note that the MIT license covers the code, not third-party brand assets, so trademark review should happen at adoption.
- How do I test Blade views that use these cryptocurrency icons?
- Because icons render as ordinary inline SVG during normal Blade rendering, you can test them like any other view. Use assertSee or assertSeeHtml on the expected SVG markup or icon symbol in your feature tests. There are no network calls at render time, so tests stay deterministic.
- What are the alternatives to this package, and when should I not use it?
- Alternatives are to vendor the SVG marks yourself, use a generic icon package, or consume an icon API in a client-side frontend. This package does not fit API-only services or SPA-first frontends that never render Blade, because it is a Blade component for server-rendered views. It also does not fit teams with a standing policy against shipping front-end assets through Composer.
Weaver
How can I help you explore Laravel packages today?