- How do I install schmeits/filament-4-phosphor-icons in a Laravel app?
- Install it with Composer using composer require schmeits/filament-4-phosphor-icons, then confirm the package constraints against your PHP, Laravel, Livewire, and exact Filament 4 or 5 version. The package is a thin presentation adapter, so most work is replacing icon strings with enum cases rather than wiring infrastructure. If the README mentions config or asset publishing, run those steps and commit the published files. Pin the package minor version before rolling it out.
- Does this package support Filament 4 and Filament 5?
- Yes, the package is described as providing Phosphor icons for Filament 4 and 5. You should still verify that its Composer constraint includes the exact Filament minor version in use, especially if you are testing a Filament 5 pre-release. Pin the package version and review changelogs before upgrading Filament majors.
- Does the Phosphor enum implement Filament's icon contract or just return strings?
- The package centers on a backed enum that maps Phosphor icon names into Filament's icon APIs, but the provided context does not confirm whether it implements Filament's icon contract directly. Check the source or README before assuming contract-level integration. In practice, you should be able to use enum cases anywhere Filament accepts icon strings, such as buttons, actions, navigation, widgets, and tables.
- How do I choose between Phosphor weights such as regular, fill, and duotone?
- The package supports all six Phosphor weights, but the context does not confirm whether each icon and weight combination is a separate enum case or selected through a method or parameter. Review the enum design before mapping your UI states. A practical mapping is regular for default icons, fill for active or selected states, and duotone for empty states or summaries.
- Can I use these Phosphor icons in Filament tables, navigation, actions, and forms?
- Yes, the package is intended for seamless use in Filament tables, navigation, actions, and other icon surfaces. It also provides a Blade icon component and an icon picker for forms. Replace hard-coded icon strings with the package enum cases and verify rendering at each Filament icon size used in your panel.
- Does the package bundle SVG assets or rely on an icon font or CDN?
- The provided context does not specify whether the package bundles SVGs, depends on npm assets, or uses a font or CDN. This matters for CSP, Vite, and asset-publishing behavior in production. Inspect the package source and README before adopting it in a tightly controlled admin panel.
- Is schmeits/filament-4-phosphor-icons safe for production use?
- Technical risk is low to moderate because runtime complexity is minimal and the package is MIT licensed. The larger concern is weak ecosystem validation: it has about 17 stars, zero dependents, and a single-maintainer profile. For business-critical admin surfaces, pin the version, review releases quarterly, and keep an internal fork or vendored enum fallback.
- How do I migrate from hard-coded icon strings or Heroicons to this package?
- Start with one low-risk Filament panel, install the package, map your top 20 icons, and replace hard-coded icon strings with enum cases. Compare rendering at every Filament size you use, including dark mode and disabled states, before codemod-ing the remaining resources, actions, and widgets. Keep the old icon strings until visual regression checks pass, and consider a lint rule that bans raw icon strings in Filament resources.
- How does this package compare with Heroicons or other Filament icon options?
- This package is Phosphor-specific and exposes all six Phosphor weights through one enum vocabulary. It is a good fit when you want Phosphor's regular, fill, and duotone styles to express design-system states, but it is a weaker fit if your product already standardizes on Heroicons. Running two icon systems indefinitely creates governance debt, so choose one icon language per panel.
- What happens if the package is abandoned or missing an icon case?
- The MIT license allows you to fork and republish the package under your own namespace if maintenance stops. Because it has zero dependents and single-maintainer support with no SLA, budget time for upstream issues and keep an internal fork mirror or vendored enum fallback. Document your fork and upgrade cadence before using it in critical admin surfaces.