- What does rolland97/filament-resource-customizer do?
- It is a Laravel Composer package that adds customization options for Filament resources plus a permissions generator, so you can tailor admin panel resource behavior and UI to your application. The stated goal is extra flexibility without editing Filament core files. Confirm the exact functional scope during a short technical spike, since the package-level behavior is not fully documented in the release notes. Treat it as a greenfield evaluation rather than a drop-in replacement for existing custom code.
- How do I install rolland97/filament-resource-customizer with Composer?
- Install it with composer require rolland97/filament-resource-customizer and pin the constraint to ^2.1. The package declares support for PHP 8.3 through 8.5 and Laravel 12 through 13, so verify your application meets those constraints first. After installation, run composer audit to review transitive dependencies. Test the install in a disposable Laravel 12 application on PHP 8.4 before touching an existing project.
- Which PHP and Laravel versions does this package support?
- The release metadata declares PHP 8.3 to 8.5 and Laravel 12 to 13, with PHP 8.5 explicitly verified in the CI matrix. PHP 8.2 and earlier are not listed as supported, so older applications would need to upgrade first. Laravel 13 support should be confirmed against your target environment before you depend on it, since 13 may be pre-release at the time of writing.
- Is this package compatible with Laravel 13?
- Laravel 13 appears in the declared support matrix and the CI pipeline exercises it alongside Laravel 12. That is a positive signal but not proof that every feature path works in your application. Confirm that Laravel 13 is available and stable in your target environments before relying on that part of the matrix. If you are on Laravel 12, treat 13 compatibility as forward-looking rather than a current requirement.
- Is upgrading from v2.1.0 to v2.1.1 safe?
- Yes. v2.1.1 is a patch release with no library code changes, so upgrade risk from v2.1.0 is effectively nil. The change is CI-only and verifies already-declared PHP 8.5 compatibility. You can bump the version without a functional regression review, though package-level risks such as dependency footprint and test depth remain unassessed.
- How do I generate permissions for Filament resources with this package?
- The package ships a permissions generator alongside its resource customization options, but the exact artisan command or API surface depends on the package documentation. Check the repository README and source for the generator entry point before wiring it into your application. Run it first against a disposable Laravel 12 project to see what it writes and whether the output matches your authorization model. Pair it with your existing policies and gates rather than replacing them outright.
- How should I test this package before adopting it in a Laravel app?
- Spin up a throwaway Laravel 12 application on PHP 8.4, install the package, and exercise both the resource customization and permissions generation paths. Run the package's own test suite plus your application integration tests, and exercise the PHP 8.5 path in CI or a sandbox if you plan to adopt 8.5. Deploy to staging behind a feature flag and monitor errors and performance before promoting to production with a documented rollback path.
- What risks should I check before using this package in production?
- The package-level risks are unassessed: dependency footprint, test depth, static analysis baseline, security disclosure process, and maintainer concentration. Dependency conflicts on future Laravel upgrades and behavior changes in minor releases despite semver are the most likely failure modes. Run composer audit, review the license, and load-test any request-path usage before broad rollout. If the package is community-maintained, establish an internal owner and a fallback plan in advance.
- Are there alternatives to this package for customizing Filament resources?
- Filament itself exposes resource, form, and table extension points that cover many customization needs without a third-party package, and custom policies or permission packages can handle authorization. Before adopting this package, compare its generator output against what you would write by hand, since custom code carries no extra dependency or maintenance risk. If you are already using a permissions library, check whether it integrates cleanly with this package's generator or duplicates it.
- Who maintains this package, and is it actively maintained?
- The repository is published under the rolland97 vendor namespace, and the v2.1.1 release shows active CI maintenance with forward-looking PHP 8.5 and Laravel 13 coverage. Release cadence and responsiveness to future Laravel major versions are not proven by a single patch release. The support model is unknown, so plan for a bus factor of one unless you can confirm otherwise. Track security advisories and Laravel and PHP end-of-life dates, and keep an internal owner for the integration.