- What does timo-de-winter/filament-modifiable-plugins do?
- It is a Filament package that lets you modify installed plugins from your admin panel, providing a centralized way to manage plugin settings and behavior without editing code. It targets Laravel applications that already use Filament and need to customize third-party plugin behavior at runtime. It is not intended for non-Laravel or non-Filament stacks.
- How do I install filament-modifiable-plugins in a Laravel app?
- Installation is standard Composer with Laravel package auto-discovery. Run the Composer require command for timo-de-winter/filament-modifiable-plugins, then verify that the package's composer.json constraints match your PHP, Laravel, and Filament versions. A sandbox proof of concept with your exact Filament version is recommended before production use.
- Which Laravel, PHP, and Filament versions does filament-modifiable-plugins support?
- The provided evaluation does not confirm exact Laravel, PHP, or Filament version constraints. You should inspect the package composer.json and test against the exact Filament version used in your application. The v5.x release line likely targets a specific Filament major version, so confirm compatibility rather than assuming it.
- Is filament-modifiable-plugins compatible with Filament v3 or v4?
- Compatibility with specific Filament majors is not confirmed in the available information. The package depends on Filament internals, so behavior can change between Filament releases. Validate it in a sandbox using your target Filament version before adding it to production.
- Can I use this package to modify third-party Filament plugins without forking them?
- Yes, the package is aimed at modifying installed Filament plugins without forking them or editing plugin code directly. It is best suited to Laravel and Filament projects that already use multiple plugins and need runtime overrides or extensions. Teams without Filament plugin experience should expect a learning curve around plugin registration and service providers.
- Are there breaking changes between v5.2.1 and v5.6.3 of filament-modifiable-plugins?
- The release notes are sparse and do not clearly document behavioral or breaking changes between v5.2.1 and v5.6.3. Review the actual GitHub diff and changelog before upgrading, and pin to a specific version in production. Avoid jumping minor versions without regression testing of your plugin modifications.
- Does filament-modifiable-plugins work with Laravel Octane and multi-tenant Filament panels?
- Support for Laravel Octane and multi-tenant Filament panels is not confirmed in the available information. Because the package hooks into Filament plugin behavior, you should test long-running workers and tenant-specific panel configurations explicitly. Run a proof of concept under your expected admin concurrency before relying on it in production.
- How does filament-modifiable-plugins resolve conflicts between multiple modified plugins?
- Conflict resolution between multiple modified plugins is not documented in the provided evaluation. Conflicts may be difficult to diagnose because debugging requires understanding both Filament internals and the package's interception layer. Document your modification patterns and test representative combinations of plugins before rollout.
- Is filament-modifiable-plugins production-ready and actively maintained?
- There are multiple releases between v5.2.1 and v5.6.3, which suggests active development. However, the project appears to be maintained by a single author, creating bus-factor risk, and support is likely community-only through GitHub issues. Track releases, designate an internal owner, and be prepared to fork or patch if maintenance lags.
- What are alternatives to filament-modifiable-plugins for customizing Filament plugins?
- Alternatives include forking the third-party plugin, using ad-hoc service-provider overrides, or relying on Filament configuration where the plugin exposes it. This package is best introduced when replacing forked plugins or ad-hoc overrides and when you want centralized runtime plugin configuration. Evaluate it in development first and keep a rollback plan.