Weave Code
Blade Bytesize Icons Laravel Package
codeat3/blade-bytesize-icons
codeat3/blade-bytesize-icons provides ready-to-use Blade components for the Bytesize SVG icon library, letting Laravel developers render clean, scalable icons in views with simple tags, customize attributes, and avoid manually embedding SVG markup.
A package to easily make use of Bytesize Icons in your Laravel Blade views.
Frequently asked questions about Blade Bytesize Icons
- How do I install codeat3/blade-bytesize-icons in a Laravel application?
- Run composer require codeat3/blade-bytesize-icons; it pulls in blade-ui-kit/blade-icons as its only real dependency. There are no migrations, no config file to publish, and no asset pipeline or npm step. After Composer finishes, the Blade components are registered and ready to use in any Blade view.
- What is the Blade syntax for rendering a Bytesize icon?
- Icons are exposed as Blade components named after the icon plus its size, for example <x-bytesize-check-16 class="size-4" />. Any attributes you add on the tag are passed through to the rendered inline SVG. The prefix keeps the tags unambiguous even when other icon packages are installed.
- How do I change the icon size, color and dark mode styling?
- The icons render as inline SVG that inherits currentColor, so color and dark mode come from your existing Tailwind or CSS text color utilities rather than package configuration. Size can be controlled with utility classes like size-4 or with explicit width and height attributes. Bytesize ships distinct components per size (16, 24 and 32), so you can also pick the variant that matches your design grid.
- Which Laravel and PHP versions does blade-bytesize-icons support?
- The package targets Laravel 10 and newer, and release 1.7.0 added declared Laravel 13 compatibility through a compatibility-only pull request with no feature or API changes. Check the illuminate/support constraint in composer.json before upgrading: if 1.7.0 widened the range you are safe on older majors, but if it hard-pivoted to ^13 it will strand Laravel 10 to 12 apps. Treat the Laravel 13 claim as declared rather than proven until one of your own apps exercises it.
- Does this package work with Livewire, Inertia or API-only projects?
- It works anywhere Laravel renders Blade server-side, which includes Livewire components since they compile to Blade templates. It does not help Inertia, React or Vue front ends that render icons client-side, and it is meaningless in an API-only service. For those setups you need a JavaScript icon solution plus a shared SVG source of truth so the Laravel and client sides stay in sync.
- Can I use blade-bytesize-icons alongside Heroicons or other icon packages?
- Yes. It is built on blade-ui-kit/blade-icons, which supports multiple icon sets registered under distinct prefixes, so Heroicons, Feather or Phosphor can coexist without conflicts. Adoption is purely additive: you add the dependency and start using the new tags. Keep an eye on how many icon dependencies you accumulate, since each one is a separate catalog to keep aligned with your design system.
- Can I override the SVG markup or accessibility attributes like aria-hidden and title?
- You can pass attributes such as class, aria-hidden, role, focusable, fill and stroke directly on the component tag, and they land on the rendered SVG root. Deeper markup changes, like adding a <title> element or replacing paths, mean publishing or overriding the underlying SVG or swapping the component. The code surface is small enough that vendoring or forking a single icon is a realistic option.
- Is codeat3/blade-bytesize-icons safe to use in production?
- The runtime risk is low because it is a presentation-only package: no service provider logic beyond component registration, no database, auth, queue or outbound network calls, and no trust boundary. The real risks are lifecycle and supply chain: a single maintainer, no documented security disclosure process and no deprecation policy. Mitigate by pinning the version and accepting that forking or replacing the package is cheap if maintenance stalls.
- Is the Bytesize icon license cleared for commercial or white-labelled distribution?
- The package itself is a thin Blade wrapper, but the icons come from the upstream Bytesize SVG set and carry their own license and any attribution requirements. Verify those terms against your distribution model, especially for customer-facing, white-labelled or redistributed builds. If attribution is required, plan where it lives in your product or docs before shipping.
- What are the alternatives to blade-bytesize-icons?
- The most direct alternatives are other blade-ui-kit/blade-icons adapters such as blade-heroicons, blade-feather-icons or blade-phosphor-icons, which use the same component approach with different catalogs. You can also drop an SVG sprite or inline partial into your own Blade components if you only need a handful of icons. Choose Bytesize if its deliberately minimal style fits your design vocabulary; otherwise pick a set whose catalog matches your icon needs and avoid carrying several icon dependencies.
Weaver
How can I help you explore Laravel packages today?