- How do I install the Statamic Heroicons addon in a Laravel app?
- Install it with Composer as a Statamic addon in your Laravel application, then follow the package's Statamic addon registration steps. Because it is a presentation-layer package, there are no migrations or external services to configure. Confirm your Statamic major version before installing, especially if you are moving to v3.3.
- Does stefangalescu/statamic-heroicons support Statamic 6 and Laravel 12?
- Version 3.3 adds Statamic 6 support, and the tested pairing for that path is Laravel 12. If you are still on Statamic 5, the release is effectively a patch-grade change you can adopt for the rendering and escaping fixes. Always verify your exact Laravel minor is inside the supported range.
- What PHP versions does this Heroicons addon support?
- The CI matrix covers PHP 8.2 through 8.5, so your runtime should be inside that window. The PHP 8.5 coverage is forward-looking, so treat it as intent rather than a validated production target until your own runtime is on 8.5. Check the package composer constraints for the definitive minimum.
- How do I render a Heroicon in an Antlers template?
- The addon provides an Antlers tag that outputs the Heroicons SVG directly in your template. Use it wherever you need a crisp, scalable icon in a Statamic view. See the README for the exact tag handle and parameter names for your version.
- How do I customize Heroicon size, style, or CSS classes?
- Heroicons ship as SVGs, so customization is typically handled through the addon's tag parameters and attributes you pass when rendering. The fieldtype covers control-panel selection, while the Antlers tag handles front-end output. Confirm the exact parameter names and supported variants in the README.
- What is the Heroicons fieldtype used for in the Statamic control panel?
- The fieldtype lets editors choose and store Heroicons as content in the control panel. Your templates then render the selected icon through the Antlers tag, keeping icon choice editorial rather than hard-coded. This is useful when different entries or pages need different icons without developer changes.
- Will upgrading to v3.3 break my existing icon markup?
- v3.3 is a minor release, but it includes behavioural corrections that can alter rendered output. SVG attribute escaping can change byte-level markup for attributes containing quotes, and the missing-variant/icon hardening changes previously broken renders into graceful ones. Run snapshot or visual regression tests on views that render icons with dynamic or optional input.
- What happens if I omit the variant or icon name in the Heroicons tag?
- v3.3 hardens tag rendering when variant or icon input is missing, so it should no longer produce a broken render. The important question is whether it renders nothing, uses a fallback, or logs a warning, because a silent graceful render can mask a genuine template bug. Verify the behaviour in your version and add template tests for optional inputs.
- Are Heroicon names case-insensitive, and can I use camelCase wildcards?
- v3.3 preserves case-insensitive icon parameters and camel-case wildcard names, which restores or maintains expected behaviour for mixed-case input. Treat this as a compatibility fix rather than a new API guarantee unless the maintainers document it as such. Test any templates that pass icon names dynamically or through wildcard includes.
- Should I pin the package version when adding Statamic 6 support?
- Yes. Supporting Statamic 6 typically expands the package's Composer constraint, so a loose constraint could silently move an app still on Statamic 5 onto the Statamic 6 path. Pin deliberately, confirm the constraint is correctly disjunctive for your supported majors, and upgrade in a branch with render-path regression tests before promoting.