- What is bezhansalleh/filament-addons used for?
- It is a collection of addons for Filament, the Laravel admin panel framework, providing extra form fields, table columns, panel widgets, traits, and formatting helpers. The intent is to replace small pieces of bespoke admin-UI code with a one-line call. Think of it as a menu of small addons to cherry-pick rather than a single library to adopt wholesale, since each addon is independently useful. It only touches the admin and presentation layer, not domain logic or request-path code.
- How do I install bezhansalleh/filament-addons in a Laravel app?
- Install it with Composer using composer require bezhansalleh/filament-addons, then register the addon or plugin provider per panel. Registration is panel-scoped, so the blast radius is confined to the panels where you explicitly enable it. Check the README for the exact snippet for your Filament version, since registration conventions differ between Filament majors.
- Does bezhansalleh/filament-addons support Laravel 10?
- Yes. Release 1.0.1 widened the framework constraint to Laravel 10 via a community PR, with the rest of the release being Dependabot CI bumps that have no runtime effect. Teams still on Laravel 9 can stay on 1.0.0 until their upgrade is scheduled, and there is no reason to rush the framework bump on this package's account. Inspect the package's composer.json to confirm constraints rather than trusting the release note, because the compatibility matrix is not formally published.
- Is bezhansalleh/filament-addons safe to use in production?
- It is reasonable for admin surfaces where a failure is inconvenient but not revenue-affecting. It is a thinly resourced, single-maintainer project with a small star count, an abbreviated changelog, and no stated test matrix. Keep the consumed surface small enough that forking stays roughly a day's work, and avoid it on anything critical. Treat it as a tier-2 dependency and pin versions.
- Which components does bezhansalleh/filament-addons ship?
- It provides form fields, table columns, panel widgets, traits, and formatting helpers, each delivered as a discrete addon. Because the pieces are independent, stability should be evaluated per addon rather than per package. Check the README for the current list, since the specific set and maturity of each piece matter more than the package as a whole.
- Does bezhansalleh/filament-addons work with both Filament 2 and Filament 3?
- Filament v2 and v3 addons are not interchangeable, so the addon you use must match the Filament major version pinned in your project. Verify the Filament constraint in the package's composer.json before upgrading either side. The compatibility matrix is not formally documented, so it must be inferred from composer constraints rather than a published support table.
- Does bezhansalleh/filament-addons require database migrations or config publishing?
- No database migrations are involved, and no config republication or code changes to existing consumers are expected for the 1.0.1 upgrade. The upgrade is a plain composer update inside the existing constraint. Individual addons may carry their own configuration or asset dependencies that could break silently under a minor bump, so check per addon before enabling it.
- Does bezhansalleh/filament-addons follow semver and have a deprecation policy?
- There is no clearly stated semver or deprecation policy for the 1.x line, and the changelog is abbreviated. The 1.0.1 release contained no breaking changes, deprecations, or new public APIs to coordinate. Pin your versions and review changelogs manually before updating. Before depending on it heavily, ask who the committers of record are beyond the primary maintainer and what the succession plan is.
- Does bezhansalleh/filament-addons support Laravel 11 and PHP 8.3?
- There is no published forward signal on Laravel 11+ or PHP 8.3 support. Laravel 10 implies PHP 8.1+, and the release notes are silent on the PHP constraint, so read the package's composer.json for the actual requirement. Treat any Laravel 11 or PHP 8.3 upgrade as something you validate yourself before relying on the addons.
- Does bezhansalleh/filament-addons have tests and CI coverage?
- The project does not publish a stated test matrix, and the 1.0.1 release consisted of a framework constraint widening plus four Dependabot CI bumps. It is unclear whether CI exercises a full Laravel plus Filament matrix or only lint and static checks. Resolve that question before committing to the package, and add your own smoke tests around whichever addons you enable.