Statamic Heroicons Laravel Package

Technical Evaluation

• Architecture fit: simonhamp/statamic-heroicons is a Statamic addon, not a general-purpose Laravel package. It fits Laravel applications that already use Statamic and need a managed Heroicons SVG set for templates/fieldtypes. Architectural footprint is likely low: icon catalog, Statamic tag/field integration, and asset/config publishing. v1.1.0 does not indicate core architecture changes; the substantive change is the bundled Heroicons v2 icon set.
• Integration feasibility: Feasible for existing Statamic sites via Composer and normal addon publishing/cache steps. The main integration work is not package installation but auditing template/content references to icon names. If the addon exposes icons through Antlers/Blade tags or a fieldtype, existing usage should be inventoried before upgrade.
• Technical risk: Medium at the template/content layer. The release is versioned as a minor update, but moving to Heroicons v2 can rename, remove, or restructure icons relative to older Heroicons versions. That can break rendered UI even without an API change in the addon. Release notes do not declare breaking changes, deprecations, or new addon APIs, but they also do not document icon-name compatibility or aliases.
• Key questions: Which Statamic, Laravel, and PHP versions are supported? Does v1.1.0 bundle Heroicons v2.0.x or a later v2 release? Are old icon names aliased? Are tag/fieldtype APIs unchanged? Are assets published/cached in a way that requires cache clearing? Are there tests or visual regression coverage for icon rendering? What is the maintenance/support model for the addon and its Heroicons dependency?

Integration Approach

• Stack fit: Good fit only for Statamic-based Laravel products. Low strategic value for non-Statamic Laravel applications; those should use Heroicons directly as SVGs or via a frontend build pipeline.
• Migration path: Pin the current working version, create an upgrade branch, install v1.1.0 in staging, and audit every icon reference in templates and content. Treat the upgrade as potentially content-breaking despite the minor version. If the addon does not alias old names, prepare a mapping table from old icon references to Heroicons v2 equivalents.
• Compatibility: Validate against the product’s Statamic and PHP matrix before rollout. Check whether published assets, config, or caches must be refreshed. If icons are selected dynamically from content, plan a data-level migration rather than only a template search.
• Sequencing: 1) Inventory icon usage and owners. 2) Review addon source/docs for tag syntax and icon-name changes. 3) Upgrade in a non-production environment. 4) Republish assets and clear Statamic/Laravel caches. 5) Run visual regression and template smoke tests. 6) Deploy behind a rollback plan, ideally with version pinning and a documented icon mapping.

Operational Impact

• Maintenance: Low ongoing code maintenance if the addon remains compatible, but icon catalog updates can create recurring template/content churn. Pin exact versions and schedule icon-reference audits when updating.
• Support: Community addon with a small maintainer base and a new contributor in this release. Internal ownership should be explicit; do not assume vendor-grade support. Keep a fallback path to plain SVG assets if the addon becomes stale.
• Scaling: Runtime impact is likely low for static SVG rendering. Watch template inlining and asset publishing if many icons are embedded; prefer cached/compiled output and avoid unnecessary per-request SVG reads.
• Failure modes: Renamed or removed icons may render empty, fall back incorrectly, or break layouts; stale published assets may keep old icons; Composer updates may introduce Statamic boot/config issues; dynamic icon names from content can fail silently. Visual regression checks are more valuable than unit tests alone for this change.
• Ramp-up: Low for Statamic developers familiar with Antlers/Blade and addon publishing. Moderate for content editors because Heroicons v2 naming differs from earlier sets; provide an approved icon list and usage examples.