- How do I install and use Health Icons in a Laravel Blade view?
- Install the package with composer require troccoli/blade-health-icons. The service provider is auto-discovered and registers the icon set as anonymous Blade components, so no manual registration is needed. You then render icons straight in your templates with tags such as <x-health-icon-name />. No SVG copying, publishing, or asset pipeline work is required for basic usage.
- Which Laravel and PHP versions does troccoli/blade-health-icons v6 support?
- v6.0.0 is a platform-matrix release: it adds Laravel 13 support and drops Laravel 11. The exact PHP floor and the full supported Laravel range are defined in the package composer.json, so check that file rather than relying on the release title alone. If your application is on Laravel 12, confirm it is still inside the v6 constraint before upgrading. The upgrade is gated entirely by the Composer solve, not by integration work.
- Does this package still support Laravel 11?
- No. v6.0.0 explicitly drops Laravel 11, so Laravel 11 applications cannot install the new major and will be resolved to the v5 line by Composer. If you are holding on Laravel 11 for security-patch-only stability, stay on v5 and confirm with the maintainer whether that branch still receives fixes. Moving to v6 means moving your application to a newer Laravel first.
- How do I change the size, color, and other attributes of a health icon?
- The icons render as inline SVG, so attributes you place on the component tag apply to the SVG output, typically class, width, height, and fill or stroke. That lets you size and recolor icons per usage without touching the package files. Check the README for the exact attribute and prop conventions before standardizing on them across a design system.
- Are the Health Icons Blade components accessible?
- Because the icons are inline SVG, you control the accessibility attributes directly on each tag. Use aria-hidden="true" for purely decorative icons and role="img" with an aria-label or title when the icon carries meaning on its own. Verify the component's default attributes in the README so you are not shipping duplicate or conflicting labels. Pair icons with visible text wherever possible.
- How is this different from blade-icons or copying SVG files manually?
- This package ships the Health Icons set as ready-made anonymous Blade components, so there is no icon registry configuration, no SVG file management, and no manual copy-paste. blade-icons is a generic SVG loading layer that can host many sets but requires you to install and configure the icon set yourself. Manual SVG embedding gives full control but drifts quickly and adds maintenance overhead. Choose this package if you specifically want the Health Icons set with minimal setup.
- Can I use these icons with Livewire, Inertia, or mail templates?
- Yes. The package is pure view-layer Blade rendering, so it works anywhere Blade runs, including Livewire components, server-rendered Inertia partials, and mail templates. It is not intended for API-only services, non-Laravel PHP projects, or front-ends that pull icons from a CDN or a design-system package. In those cases treat it as out of scope rather than forcing it in.
- How do I test that health icons render correctly in my Blade views?
- Render the view or page in a feature test and assert on the inline SVG output, for example with assertSee or assertSeeHtml against a known path or class. You can also render a single component in isolation to confirm the tag name and attributes you rely on. Keep assertions loose on markup details that may change between icon set syncs, and tight on the behavior you actually depend on, such as a specific class or aria attribute.
- What happens in production if an icon component fails to render?
- The blast radius is cosmetic: an icon does not appear, and nothing in a transactional or data path is affected. The package adds no routes, migrations, middleware, or boot-time services beyond component namespace registration. The one edge case is calling an unknown component inside a view with strict exception handling, which can surface as an error, so avoid dynamic component names built from user input.
- Is troccoli/blade-health-icons actively maintained, and how do breaking changes work?
- It is a single-maintainer package that treats support-matrix changes as major versions, so every Laravel major will likely force a Composer constraint decision on your side. That cost is small but predictable, so schedule it rather than discovering it during an unrelated framework upgrade. Pin the version and rely on your lockfile, since the project has low redundancy and no meaningful supply-chain surface beyond the package itself.