- How do I install alexazartsev/heroicon in a Laravel app?
- Install it with Composer using the package name alexazartsev/heroicon. It is a Composer-only integration with no domain logic, migrations, queues, or external services described. For Nova usage, follow the version pairing: ^1.x for Nova 3 and ^2.x for Nova 4. Rebuild frontend assets after installing or upgrading because the package ships presentation assets and style changes.
- How do I render a Heroicon in a Blade template with a custom size and CSS classes?
- Use the package's Blade component to render outline or solid Heroicons and pass custom size and CSS class attributes. The component outputs SVG, so you can drop icons into Blade templates without copying SVG markup. If you use it in Nova, confirm whether your icons are rendered through the Nova field or asset integration or directly in Blade views.
- Does alexazartsev/heroicon support both outline and solid Heroicons?
- Yes. The package provides a Blade component for rendering both outline and solid Heroicons SVG variants. You choose the variant per icon and can apply custom sizing and CSS classes. This is useful for keeping icon usage consistent across an admin panel or public Laravel views.
- Is alexazartsev/heroicon only for Laravel Nova, or can I use it in regular Blade views?
- The package overview describes a Laravel Blade component for Heroicons, so direct Blade usage is the core use case. The technical evaluation also describes it as a Nova presentation and asset helper, so it fits inside Laravel Nova admin panels. Confirm your intended usage before adopting it because the package name suggests Nova-only in some contexts while the overview describes general Blade rendering.
- Which version of alexazartsev/heroicon works with Laravel Nova 3 versus Nova 4?
- The version pairing is strict: ^1.x aligns with Laravel Nova 3 and ^2.x aligns with Nova 4. v2.0.0 deliberately drops Nova 3 support rather than supporting both, so a single shared constraint cannot span mixed Nova versions. Upgrade the host app to Nova 4 first, then bump heroicon to ^2.0.
- What happens if I upgrade alexazartsev/heroicon to ^2.0 on a Nova 3 app?
- Composer resolution should fail loudly if you try to install ^2.0 on a host still constrained to Nova 3. That failure is safe because it prevents an unsupported combination. The riskier scenario is an opportunistic composer update in a repo with a loose Nova constraint that permits the package bump unintentionally. Pin the heroicon constraint explicitly per repository and sequence the Nova 4 upgrade first.
- Why do some stored icon names render blank after upgrading alexazartsev/heroicon?
- The v2 changelog mentions fixing a few Heroicons, and any renamed or removed icon slug can leave stored icon identifiers unresolved. In that case the UI may render a blank icon rather than throwing an error. Enumerate durable icon names in config, database columns, seeders, and Nova resource settings, then verify each still resolves after upgrade.
- Does the fill='currentColor' change affect dark mode or custom CSS?
- The switch to fill='currentColor' and the light and dark theme style changes can alter rendering for all existing icons, not just newly added ones. Expect cosmetic differences, especially in dark mode or where custom CSS previously relied on a hardcoded fill color. Treat it as a visual regression check and decide whether theme-aware tinting is desirable for your panels.
- How should I test and roll out alexazartsev/heroicon safely in production?
- Upgrade in a branch, rebuild and purge published vendor assets, and compare rendered icons in both light and dark themes before production. Because the blast radius is visual rather than functional, focus on screenshots or visual regression checks for Nova panels and Blade views that use icons. Also test Composer resolution in each repo separately if you run mixed Nova versions.
- Is alexazartsev/heroicon actively maintained, and what are the alternatives?
- The package has a single maintainer and no clearly stated test matrix in the provided context, so maintenance is a medium risk. A future Nova major release could repeat the breaking cutover pattern seen from v1 to v2. Alternatives include using Heroicons directly as SVG or Blade partials, another maintained Heroicons Blade package, or owning a small fork if you need guaranteed upgrade support.