Weave Code
Blade Mono Icons Laravel Package
codeat3/blade-mono-icons
Laravel Blade package that provides ready-to-use components for the Mono Icons set, making it easy to render crisp SVG icons directly in Blade templates with customizable size, color, and attributes—no manual SVG copying or extra setup required.
A package to easily make use of Mono Icons in your Laravel Blade views.
Frequently asked questions about Blade Mono Icons
- How do I install and use codeat3/blade-mono-icons in a Laravel app?
- Run composer require codeat3/blade-mono-icons and the service provider is auto-discovered, so no manual registration or configuration is needed. Then drop an icon into any Blade template using the component syntax, for example a mono icon tag such as <x-mono-... />. The package renders inline SVGs server-side, so there is no JavaScript build step or asset pipeline change involved.
- Which Laravel versions does codeat3/blade-mono-icons support?
- Laravel 10 through 12 are supported today, with Laravel 13 opened up in version 1.6.0. However, the usable window is the intersection of this package's illuminate/* constraints and those of its blade-ui-kit/blade-icons dependency. Read both composer.json files before assuming a Laravel 13 upgrade will resolve.
- How do I change the size and color of a Mono icon in Blade?
- Icon components forward size and color attributes, so you can set them directly on the tag, for example with width, height, or a Tailwind class like text-blue-500. The underlying SVGs inherit currentColor, which means color theming stays in your CSS rather than in package config. Any extra SVG attributes you pass are forwarded to the rendered element.
- What component prefix does blade-mono-icons use, and will it collide with other icon packages?
- Components are exposed under the package's mono icon namespace, rendered as <x-mono-...> tags in your templates. If you already use another blade-* icon package, the two are additive because each keeps its own component namespace. Still check the default prefix against what is installed, since identical prefixes would cause a class or view collision.
- Do I need to publish config or assets for blade-mono-icons to work?
- No. The default install path has no config surface and no published assets because the icons ship as static, vendored SVGs rendered inline at runtime. There are no migrations, queues, scheduled jobs, outbound HTTP calls, or credentials involved. That means nothing to publish and nothing to add to your deployment checklist.
- How do I pass extra classes or attributes like aria-hidden to a Mono icon component?
- Attributes you add to the component tag are forwarded to the rendered svg element, so class, aria-hidden, role, or focusable all work as expected. Tailwind utilities therefore apply directly to the icon without a wrapper element. Remember that accessibility is the consuming team's responsibility: icons render as decorative SVGs, so add aria-label or visible text yourself where meaning matters.
- Does blade-mono-icons work with Tailwind CSS and dark mode?
- Yes. Because the SVGs use currentColor and forward class attributes, Tailwind utilities such as text-gray-500 or dark:text-white control the rendered icon. No package configuration is required for theming; styling stays entirely in your CSS. This also keeps the package out of your design tokens discussion.
- How do I test that Mono icon components render correctly in Laravel?
- A single feature test is usually enough: hit a route or render a view that includes one or more icon components, assert a 200 response, and assert the expected svg markup appears in the output. Because the icons are static inline SVG, the assertions are stable and need no mocking. This also catches namespace or prefix collisions early if other icon packages are installed.
- Is blade-mono-icons compatible with Laravel 13, and what should I check before upgrading?
- Version 1.6.0 only widened this package's own constraints, so Laravel 13 support depends on blade-ui-kit/blade-icons also declaring Laravel 13 compatibility. Read the composer.json diff rather than the changelog to confirm whether the PHP floor or the blade-icons pin changed as well. On a Laravel 13 skeleton, verify which blade-icons version resolves before committing to the platform upgrade.
- What are the alternatives to blade-mono-icons, and can I fork or vendor it?
- Alternatives include hand-pasted inline SVG blocks, an SVG sprite sheet, other blade-* icon packages built on blade-icons, or pulling the Mono Icons set from npm in an SPA front end. If you need an escape hatch, the package payload is static SVG data in a single maintainer repo, so it can be forked or vendored without rewriting consumer templates. That keeps exit cost low, though pinning versions and wrapping usage in one internal component limits icon-set drift on minor bumps.
Weaver
How can I help you explore Laravel packages today?