Weave Code
Blade Forkawesome Laravel Package
codeat3/blade-forkawesome
Render Fork Awesome icons anywhere in your Laravel Blade views with this lightweight package. It wraps the Fork Awesome icon set in simple Blade components and directives, letting you drop scalable, styleable icons into templates without extra setup. Install via Composer and use icons in seconds.
A package to easily make use of "Fork Awesome Icons" in your Laravel Blade views.
Frequently asked questions about Blade Forkawesome
- How do I install codeat3/blade-forkawesome in a Laravel app?
- Run composer require codeat3/blade-forkawesome. Laravel package auto-discovery registers the service provider automatically, so you do not need to add anything to config/app.php or publish a config file. You can render an icon in a Blade view immediately after the install finishes.
- Which Laravel versions does blade-forkawesome support?
- The package installs on Laravel 5.5 and later via package auto-discovery, and the 1.12.0 release widens the constraint to allow Laravel 13 while staying backwards compatible with the 1.11.x line, so L8 through L12 installs are unaffected. One caveat: Laravel 13 support is only as real as the blade-ui-kit/blade-icons version it pulls in, so confirm that dependency is also L13-ready before treating this release as an upgrade green light.
- How do I render a Fork Awesome icon inside a Blade template?
- Use the registered Blade component syntax, for example <x-forkawesome-github />. Each Fork Awesome glyph is exposed as its own component through blade-ui-kit/blade-icons, so you reference icons by name instead of by CSS class. Check the generated component names against the actual bundled file list rather than assuming Font Awesome style class names.
- Can I change the size, color, or CSS class of a Fork Awesome icon?
- Yes. Any HTML attributes you pass to the component, such as class, width, height, fill, or style, are forwarded to the rendered SVG element. That lets you size and recolor icons with inline attributes or your existing Tailwind and CSS utility classes. Because the output is inline SVG, icons stay crisp at any scale and are fully styleable.
- Do I need to register a service provider or publish config for blade-forkawesome?
- No. The service provider is registered through Laravel package auto-discovery, so there is no manual registration step. Publishing the config is optional and only matters if you want to override the icon path or the component prefix. The package has no database, queue, API key, or external service behind it.
- Does blade-forkawesome make CDN or network requests at runtime?
- No. The Fork Awesome glyphs ship as static SVG files inside the package and are rendered inline into your HTML, so there is no CDN call and no runtime network dependency. That makes it safe for offline and air-gapped deployments and removes a third-party availability risk from your stack.
- What is the difference between blade-forkawesome and blade-fontawesome?
- Both packages come from the same maintainer and share the same thin wrapper over blade-ui-kit/blade-icons; the difference is which icon set is bundled. blade-forkawesome ships Fork Awesome, a community fork of Font Awesome 4.7, while blade-fontawesome ships the Font Awesome glyphs. Pick based on the icon designs your UI already uses, and note that switching later is largely a matter of changing the component prefix if you wrap icons in your own partial.
- Is Fork Awesome still maintained, and will new icons be added?
- Fork Awesome is effectively frozen upstream, so you should not expect new glyphs. That is a design staleness risk rather than a stability risk, because the bundled static SVGs do not rot or break. Treat the package as a versioned icon library and a stopgap if iconography modernization sits anywhere on your roadmap.
- What is the license for the Fork Awesome icons bundled in this package?
- The package itself is MIT licensed, but the bundled SVG glyphs follow Fork Awesome's own licensing, which differs from the Font Awesome 4.7 lineage it forked. Confirm the SVG license and any attribution obligation before shipping in a commercial or redistributed product. This is the one item that can genuinely halt adoption, so resolve it before you build on the package.
- Can I use blade-forkawesome with Livewire or Inertia?
- Yes. It is a pure Blade component package, so it works anywhere Blade renders, including plain server-rendered views, Livewire components, and Inertia layouts. There is no JavaScript, bundler configuration, or asset compilation step involved, so nothing extra needs wiring into your frontend build.
Weaver
How can I help you explore Laravel packages today?