Weave Code
Filament Hugeicons Icons Laravel Package
filafly/filament-hugeicons-icons
filafly/filament-hugeicons-icons brings the Hugeicons icon set to Filament, making a large library of consistently designed icons available for Laravel admin panels, forms, tables, and actions. Use Hugeicons seamlessly across Filament UI components.
At a glance
Frequently asked questions about Filament Hugeicons Icons
- How do I install filafly/filament-hugeicons-icons in a Laravel application?
- Install it with Composer using composer require filafly/filament-hugeicons-icons. The package ships a service provider with Laravel package auto-discovery, so no manual provider registration is usually needed. After installing, register the plugin in your Filament panel provider so its icon set is available to the panel. Commit the updated composer.json and composer.lock so other environments resolve the same version.
- Does this package support both Filament 4 and Filament 5?
- Yes. Version 1.1.0 adds Filament 5 support alongside existing Filament 4 support, which means the Composer constraint allows both majors in a single release. Confirm which major your application actually resolves to before upgrading, since that decides whether this is a patch-level bump or part of a larger Filament upgrade chain. Check the repository's CI matrix to see whether both majors are actually tested.
- How do I register the Hugeicons plugin in a Filament panel provider?
- Registration follows the standard Filament plugin pattern: add the package's plugin class to the plugin() call inside your Panel Provider. Check the README for the exact class name and any optional configuration arguments, as the excerpt may not list them. Once registered, Hugeicons names become selectable wherever Filament accepts an icon.
- Do I need to publish config or compiled assets after installing?
- Many Filament plugins ship precompiled CSS and JavaScript and may also offer publishable config or asset files. Run the vendor:publish command documented in the README if one is provided, then rebuild your own asset pipeline so your panel picks up the new styles. Stale compiled assets are the most common cause of icons looking broken even when the package is installed correctly.
- Where can I use Hugeicons inside a Filament panel?
- You can use them anywhere Filament accepts an icon identifier, which typically includes navigation group and item icons, action buttons, icon columns, and icon picker form fields. Because Hugeicons is a large, consistently designed set, it is a good fit for admin panels that want a uniform visual language across forms, tables, and actions. Refer to the README for the naming convention used to reference individual icons.
- What PHP, Laravel, and Livewire versions are required?
- The minimums are driven by the Filament major you are on, since Filament 4 and 5 have their own Laravel, PHP, and Livewire requirements. In practice this means a modern Laravel application on PHP 8.2 or newer with a current Livewire release. Verify the exact constraints per path with composer show filafly/filament-hugeicons-icons before committing to an upgrade.
- Is this package safe to run in production?
- It is a conventional Filament plugin with no new runtime service or datastore, so the integration surface is small. The main production risk is cosmetic: if the shipped compiled assets were built against a different Filament major, panels can render with subtly broken styling that unit tests will not catch. Pin the version, verify on a staging panel, and roll out behind a feature flag or to internal users first.
- How do I test that Hugeicons render correctly after a Filament upgrade?
- Run your existing automated test suite, then do a scripted manual or screenshot-diff pass over every screen where icons appear, including navigation, tables, and action buttons. Unit tests generally confirm an icon name is accepted but not that the glyph and styling actually render, so visual checks matter here. Also rebuild and republish assets before you judge the result, since stale bundles produce false negatives.
- How does this compare to other icon packages for Filament?
- The differentiator is the icon set itself: Hugeicons offers a large, consistently designed library rather than the smaller Heroicons-derived sets many Filament projects start with. The other factor is dual-major support, since v1.1.0 targets Filament 4 and 5 in one release, which matters if you are mid-upgrade. If your team already standardizes on another icon package, evaluate whether mixing sets is worth the visual inconsistency.
- Who maintains this package and how actively is it supported?
- It is maintained by Filafly, with version 1.1.0 being the current release that introduced Filament 5 support. Before adopting it, check the repository for release cadence, the CI matrix, and any published deprecation timeline for Filament 4 support. Those signals tell you how quickly the package will track future Filament majors.
Weaver
How can I help you explore Laravel packages today?