- What are the requirements to install Filament Flex Fields?
- Filament Flex Fields requires PHP 8.3 or newer, Laravel 11 or newer, and a Filament v5 panel. Installation is a Composer require, publishing the config and prebuilt assets, then registering the plugin on your panel provider. No queue workers, service layer, or database migration are needed for the standalone form fields.
- Does Filament Flex Fields work with Filament v4 or Laravel 10?
- No. The package targets Filament v5 only and lists Laravel 11+ and PHP 8.3+ as its baseline. If your admin panel is still on Filament v4 you would need to upgrade Filament first. For Blade, Livewire, Nova, or custom admin stacks the package does not apply at all.
- How many form components does Filament Flex Fields actually include?
- The README and package description are inconsistent, citing both 70 custom components and 79 components in different places. Confirm the real count against the per-component documentation before planning a migration. The real value is consolidation: map pickers, signature pads, media uploaders, and async selects all come from one plugin instead of several single-purpose field plugins.
- How does the virtualized Select with async search work?
- It is a client component that calls a server-side search endpoint you provide, so the result shape, pagination, debounce, and authorization are your contract to implement. That makes it the component most likely to need custom work inside an existing application. Expect to write and test the search query yourself rather than getting async search out of the box.
- Do I need Node.js or an npm build step in production?
- No. The package ships prebuilt CSS and JS that are lazy-loaded, so there is no frontend build step in your deploy pipeline. The trade-off is that you inherit the vendor's asset lifecycle and any version skew with Filament's own Tailwind build. A strict Content Security Policy that blocks dynamically injected styles can also cause hard-to-diagnose visual breakage.
- Does Filament Flex Fields integrate with Spatie Media Library and S3 uploads?
- Yes, it offers Spatie Media Library integration plus disk and S3 upload support. If you already use Spatie this is a straight win; if you do not, it becomes a transitive dependency decision you now own. Either way you still own bucket policy, path conventions, presigned URL configuration, retention, and malware scanning.
- What are JSON custom fields without EAV, and when should I use them?
- They store per-record custom field values in a JSON column instead of EAV tables, which avoids the classic multi-join pain and gives schema flexibility per record. You can adopt this path independently of the other components, which makes it a clean seam for a phased rollout. The cost moves into validation, indexing, and reporting rather than the data model, so plan for those before shipping.
- Can I use Filament Flex Fields in production with a proprietary license?
- The license is the gating risk and it is unresolved: GitHub reports NOASSERTION while the README badge says proprietary, which are contradictory signals. Get explicit written terms covering usage scope, per-app versus per-seat pricing, modification rights, renewal and expiry behavior, and source access or escrow before scheduling production work. A proprietary dependency you cannot fork or patch is an operational constraint, not a footnote.
- What is the maintenance and upgrade risk of Filament Flex Fields?
- It has a single maintainer, a small star count, no dependents, and a brand-new Filament v5 target, so there is no observable production usage to borrow confidence from. Version pinning risk is doubled because the package tracks Filament v5, which is itself young. When Filament v6 or a breaking Livewire change lands, you are waiting on one person to unblock your admin panel.
- Is there a Playground to preview the components before installing?
- Yes, the package includes a built-in Playground, and the hosted documentation at flex-fields.bjanczak.com covers each component individually. Use it to check rendering, theming, and behavior against your Filament panel version before committing to the dependency. It is a preview surface, not a substitute for testing against your own data, storage, and search endpoints.