- How do I install abduns/hugeicons-flux in a Laravel app?
- Install it with Composer using composer require abduns/hugeicons-flux. The package ships a service provider that registers anonymous Blade components under the flux component namespace with a hugeicons prefix, so you can immediately render flux:icon.hugeicons.home-01. You need a Laravel app using Flux UI 2; check the pinned package's composer.json for the exact PHP and Laravel constraints rather than relying on the README. No Node toolchain is required for the free Stroke Rounded set.
- Do I need a Hugeicons Pro licence to use this package?
- No, the free Stroke Rounded set of more than 5,100 icons is bundled and works after a Composer-only install. A Hugeicons Pro licence is only needed if you want to generate the nine Pro styles. The Pro workflow reads @hugeicons-pro/core-* packages from node_modules and uses HUGEICONS_PRO_LICENSE_KEY as a build or CI secret, not a runtime secret.
- How do I use a Hugeicons icon on a Flux button or navlist item?
- Pass the icon name through the icon prop using the hugeicons prefix, for example set icon to hugeicons.calendar-03 on flux:button or flux:navlist.item. You can also use the dedicated component syntax flux:icon.hugeicons.home-01 and style it like any Flux icon with classes such as size-10 and text-blue-500. This works because the package registers components into Flux's existing component namespace.
- How do Hugeicons names map to flux:icon.hugeicons component names?
- The package uses kebab-case versions of the Hugeicons names. Home01Icon becomes home-01, and AiSearch02Icon becomes ai-search-02. You then render them as flux:icon.hugeicons.home-01 or as an icon prop value like hugeicons.calendar-03. Check the bundled icon list if a name does not resolve as expected.
- Which Flux icon variants does the variant prop support?
- The variant prop maps Flux's outline, solid, mini, and micro aliases onto the real Hugeicons style names. If a requested Pro style is missing, the package falls back gracefully to stroke-rounded. That fallback keeps rendering working, but it also means a misconfigured licence or missing generated style can go unnoticed unless you inspect the output.
- How do I generate the Pro Hugeicons styles with hugeicons:build?
- Install and authenticate the optional @hugeicons-pro/core-* npm packages against npm.hugeicons.com, then run php artisan hugeicons:build. The command reads those packages from node_modules and emits .blade.php files into your application's resources/views/flux directory, where they override the bundled free icons because app views are resolved before package views. You must commit the generated files, and the build adds a Node toolchain plus secret management to a PHP UI concern. The generator parses third-party package structures, so re-run and review it when Hugeicons package internals change.
- Does this package support Laravel 11 and PHP 8.2?
- The README indicates PHP 8.2+ and Laravel 11+ with Flux UI 2, but the changelog says version 1.0.5 dropped PHP 8.2 in a patch release. Treat secondary docs as unreliable and verify the actual constraints in composer.json for the exact version you pin. Also note that patch releases have made consumer-breaking changes, including a component prefix rename, so a routine composer update deserves CI coverage.
- Is abduns/hugeicons-flux safe to use in production?
- It is technically plausible and low-blast-radius because the integration surface is only icons, so it is cheap to trial and reverse. The bigger risks are release hygiene, a single maintainer, zero stars and dependents, and reliance on Flux's component namespace registration and view-resolution precedence, which could change in a Flux major. Use it in a guardrailed spike first, pin a version, and have a fork or vendor fallback if you standardise on it. Its silent fallback to stroke-rounded also makes monitoring and review important.
- What licence does this package use, and can I commit generated Pro files?
- The README says MIT, but the package metadata says NOASSERTION, so legal or procurement should resolve that discrepancy before distribution. Separately, Hugeicons' own licence terms govern the icon assets, including any generated Pro Blade files you commit to your repository. Confirm redistribution rights with Hugeicons before committing Pro output, and do not assume the package licence covers the icons.
- How many icons are bundled, and will that affect vendor size or IDE indexing?
- The package bundles more than 5,100 free Stroke Rounded icons under resources/views/flux/icon/hugeicons, so expect a meaningful number of files in vendor. That can affect vendor size, IDE indexing, and opcache behaviour, so measure it in your application rather than assuming it is negligible. If the footprint matters, consider whether you need the full bundled set or only the generated Pro subset you actually use.