Weave Code
Phosphoricons Laravel Package
wireui/phosphoricons
WireUI Phosphor Icons brings the Phosphor icon library to Laravel Blade through WireUI components. Use thousands of crisp SVG icons with simple Blade tags, customizing size, color, weight, and style in any Laravel app.
The phosphoricons made for laravel blade by WireUI
Frequently asked questions about Phosphoricons
- How do I install wireui/phosphoricons in a Laravel application?
- Install it with composer require wireui/phosphoricons. The package is auto-discovered, so Laravel registers the service provider and Blade components without any manual provider edits. There are no migrations, no credentials, and no external services to configure, so you can start using the icon tags immediately after the Composer install completes.
- Which Laravel and PHP versions does wireui/phosphoricons support?
- The package targets Laravel 9 through 13 on PHP 8.1 and above, with v2.5.0 being the release that declares Laravel 13 support. Before upgrading, confirm that the new constraint widens the illuminate/* range rather than replacing older versions, otherwise applications on Laravel 11 or 12 could be stranded. Also verify that sibling packages pinning illuminate/support, such as wireui/wireui, Filament, and Nova, resolve at the same time.
- How do I render a Phosphor icon in a Blade template?
- Use the registered Blade component syntax, for example an x-phosphor tag naming the icon you want, which outputs an inline SVG at render time. Because these are ordinary anonymous Blade components, they work in any Blade view, inside Livewire components, in Inertia page templates rendered through Blade, and in mail or Markdown templates. There is no JavaScript initialization step and no client-side hydration involved.
- How do I change the size, color, and CSS classes of a Phosphor icon?
- Pass familiar HTML attributes such as size, color, and class directly on the component tag, and they are applied to the rendered SVG element. That means you can size icons inline for a one-off case or lean on utility classes and Tailwind for consistent styling across views. Color handling follows the SVG stroke, so icons also inherit the surrounding text color where no explicit color is given.
- Can I use different Phosphor icon weights and styles, such as thin, light, bold, fill, or duotone?
- Yes. The package ships the full Phosphor Icons collection with multiple weights and styles, and each weight is exposed as its own component variant so you choose it in the tag rather than through CSS. That keeps the rendered markup as pure inline SVG with no runtime weight switching. Check the package's component listing for the exact naming pattern used for the weight you need.
- Does wireui/phosphoricons require Livewire or the WireUI component library?
- No. It is a standalone Blade component package that works in any Laravel application, and it simply fits naturally alongside Livewire and WireUI projects. If you already use WireUI, the icon components complement the existing form and UI components, but installing WireUI itself is not a dependency for rendering icons.
- Do Phosphor icons in Laravel need an icon font or extra JavaScript?
- No. Every icon is rendered as inline SVG markup, so there is no icon font file to load, no JavaScript bundle, and no additional network request for the icon asset. Inline SVG stays sharp at any size and scales cleanly on high-DPI screens. The trade-off is slightly larger HTML output, which is rarely significant for navigation, tables, and empty states.
- Is upgrading from wireui/phosphoricons v2.4.0 to v2.5.0 safe?
- It is a patch-level upgrade: run composer update wireui/phosphoricons and expect no code changes and no configuration republication. The v2.5.0 change is a framework-support declaration for Laravel 13, not an API or icon-set change, so apps staying on Laravel 9 through 12 should see a no-op. Clear and rebuild view caches in staging after deploying, since compiled Blade views can retain stale component references.
- How hard is it to migrate to wireui/phosphoricons from Blade Icons, Heroicons, or Font Awesome?
- The mechanics are simple because the swap is a tag replacement, but budget real time for name mapping across your icon inventory. Phosphor uses its own icon names, so expect to audit each usage and manually match it to the closest equivalent. Also review any custom SVGs or CSS that was sized against the previous icon set, and snapshot or visually regression-test the icon-bearing views such as navigation, tables, empty states, and emails.
- Is wireui/phosphoricons production-ready and how is it maintained?
- Architecturally the risk is low: it is a presentational package that touches only the view layer, with no persistence, queues, events, or middleware, and it is trivially swappable if you change your mind. Support is community OSS through GitHub issues with no vendor SLA or formal security disclosure process beyond standard GitHub advisories. Note that v2.5.0 was a single-commit release from a first-time contributor that only changed framework support, so confirm the CI matrix actually exercises Laravel 13 rather than accepting an untested support claim.
Weaver
How can I help you explore Laravel packages today?