Weave Code
Blade Maki Icons Laravel Package
codeat3/blade-maki-icons
Blade Maki Icons provides ready-to-use Blade components for the complete Maki icon set, letting you drop clean SVG map and UI icons into Laravel views with a simple tag, customizable size, color, and attributes, no extra setup required.
A package to easily make use of Maki Icons in your Laravel Blade views.
Frequently asked questions about Blade Maki Icons
- How do I install codeat3/blade-maki-icons in a Laravel application?
- Install it with Composer using composer require codeat3/blade-maki-icons. Laravel package auto-discovery registers the service provider, so there is no publish step, environment variable, or asset-build change required. You can then use the maki-prefixed Blade components directly in your views.
- Which Laravel versions does blade-maki-icons support?
- Release 1.10.0 is a compatibility-only update that widens the framework constraint for Laravel 13 without changing components, icons, or APIs. Before that release, the package could block Laravel 13 at Composer resolution. Check that your PHP runtime floor satisfies the constraint and that no other dependency still pins illuminate/support to older versions.
- How do I render a Maki icon in a Blade view?
- Use the package's maki-prefixed Blade component tag directly in your template. The component renders static SVG markup server-side, so no JavaScript bundle or client-side hydration is involved. The package is intended to drop clean map and UI icons into Laravel views with no extra setup.
- Can I customize the size, color, and attributes of a Maki icon?
- Yes. The Blade components support customizable size, color, and attribute passthrough, including class and other HTML attributes. This lets you style icons through your existing design system rather than hard-coding presentation. Validate attribute passthrough during your initial spike on a real page.
- Does blade-maki-icons require a JavaScript build step or published assets?
- No. The package sits entirely in the view layer and renders static SVG paths server-side. It adds no routes, migrations, config files, queues, scheduled jobs, or runtime services. That also means no client-side bundle growth and no hydration concerns.
- Is blade-maki-icons safe to use in production?
- Technically the risk is low because the dependency only affects rendered markup and cannot perturb domain logic, data contracts, or service-level objectives. The main governance concerns are single-maintainer continuity and upgrade gatekeeping on future Laravel majors. The fallback is straightforward: vendor the static SVG directory or fork the thin wrapper.
- What is the Maki icon set best used for in a Laravel app?
- Maki is a map and POI glyph collection with a slow upstream cadence, so it fits map, geolocation, venue-locator, delivery-tracking, and logistics surfaces. It is not a general UI icon library and will under-deliver on navigation, forms, and media controls. Adopt it for those specific surfaces to avoid creating a second redundant icon dependency.
- How should I test blade-maki-icons in my Laravel application?
- Run a smoke test by installing the package, rendering a representative icon set on a real page, and confirming attribute passthrough for class and size. Rendered-output risk between 1.9.0 and 1.10.0 is effectively nil, so a full design QA pass is not needed for the compatibility release. Assert the expected SVG markup in your view tests where it matters.
- What are alternatives to blade-maki-icons?
- Every Maki glyph can be reproduced as a hand-written inline SVG partial, so the package is a design-system hygiene decision rather than a capability bet. Other icon packages may cover broader UI needs, but they add their own dependency and namespace considerations. Vendoring the SVG directory or forking the wrapper is also a viable exit path.
- Who maintains blade-maki-icons and what happens if maintenance stops?
- The package has a single maintainer and is part of a family of icon packages generated from upstream open-source sets. Continuity depends on that person rather than an organisation, so treat it as a governance risk separate from technical risk. Because the payload is static SVG data, vendoring the icon directory or forking the thin wrapper is a days-scale exit.
Weaver
How can I help you explore Laravel packages today?