- Does krystal-sf/ux-fontawesome work with Laravel?
- No. It is a Symfony UX icon-set provider built around Twig and symfony/ux-icons, so a Laravel application gets no service provider auto-discovery, no Blade component, and no Vite or AssetMapper equivalent. Composer will install it, but Laravel will never call into it. The only reusable part is the vendored Font Awesome Free assets, which you can get from the npm package with less friction.
- How do I install and register krystal-sf/ux-fontawesome?
- In a Symfony app you install it with composer require krystal-sf/ux-fontawesome, register the bundle, and render icons through ux_icon or the package's FontAwesome Twig component. There is no equivalent registration step in Laravel because the package ships no Laravel service provider or facade. Check the repository README for the exact bundle registration and Twig syntax before wiring it into templates.
- How do I configure icon style, size, and color with this package?
- The Twig component exposes options for icon style (solid, regular, or brand), size, and color, so you set them per call instead of hand-writing class strings. Sensible defaults mean most icons render from a minimal tag. Confirm the exact option names against the package documentation, since the component API has no third-party regression coverage.
- What is the Font Awesome icon prefix and can I change it?
- The prefix comes from the icon set class, typically fa, and it determines every template string you write. A mismatch between the configured prefix and the icon name surfaces at render time as an IconNotFoundException on live pages rather than at build time. Verify in the source whether getPrefix() is fixed or configurable before standardising templates on it.
- Which Symfony, PHP, and Font Awesome versions does it support?
- The package depends on symfony/ux-icons and the Symfony asset pipeline, but its declared Symfony and PHP ranges are not documented in the overview, so read composer.json before adopting it. Undocumented constraints matter because a minor Symfony or UX Icons bump can change asset paths or icon registration silently. Pin the Font Awesome Free version too, since glyphs can shift between major releases.
- What are the Font Awesome licensing requirements for production?
- This is the part teams usually miss. The Font Awesome Free icons are CC BY 4.0, the fonts are SIL OFL 1.1, and the package's own code is MIT, so attribution obligations flow through to whatever product ships the icons. If the assets compile into a Laravel Vite build, confirm the licence headers and attribution files survive the build.
- How do I test icon rendering and catch IconNotFoundException before production?
- Icons resolve at render time, so a wrong prefix or missing icon set throws IconNotFoundException in production rather than failing the build. Add a smoke test that renders every icon you use, or a template lint pass that validates your icon names against the icon set. If you are on Laravel, test the Blade component output instead, since the Symfony code path does not apply.
- How do I render Font Awesome icons in Laravel without this package?
- Install @fortawesome/fontawesome-free with npm, import its CSS in resources/js/app.js, then render icons through a small Blade component or a maintained catalogue such as blade-ui-kit/blade-icons. That keeps the asset pipeline under Vite, avoids framework coupling, and removes the package from your Composer audit surface. It is roughly an afternoon of work and gives you full control of upgrades.
- Is krystal-sf/ux-fontawesome actively maintained and safe to depend on?
- Treat it as internal tooling until proven otherwise. It has zero stars, zero dependents, and single-org provenance from Krystal, with no visible public issue history, release cadence, or security policy. Ask directly whether it is published publicly for convenience, and who owns the upgrade when Symfony, UX Icons, or Font Awesome ships a major version.
- What is the migration or rollback path if the package is archived?
- If Krystal archives the repository, your rollback is either vendoring the Font Awesome Free assets directly or switching to the npm package plus a Blade component, so plan for replacement rather than a fork you have to maintain. Moving a Symfony service to Laravel means replacing ux_icon calls with Blade components, swapping AssetMapper or Encore for Vite, and pinning an identical Font Awesome version so rendered glyphs do not shift mid-migration.