- Does this package work with Filament v4 or earlier?
- No, this package is strictly for Filament v5 only. There are no plans to backport it to Filament v3 or v4. Ensure your project is using Filament v5 before installing.
- How do I install and set up Filament Flux in my Laravel project?
- Run `composer require jeffersongoncalves/filament-flux`, then execute `php artisan make:filament-theme admin` and `php artisan filament-flux:install --panel=admin`. Finally, run `npm run build` to inject Flux styles into your theme CSS.
- Can I use Flux components selectively instead of replacing everything?
- Yes, the package supports granular opt-in replacements. You can enable Flux components for specific fields, tables, or actions while keeping others as native Filament components. This reduces risk during migration.
- What Laravel and PHP versions are supported?
- This package requires Laravel 11, 12, or 13, PHP 8.2+, Livewire 4.0+, and Flux 2.14+. Ensure your project meets these requirements before installation to avoid compatibility issues.
- Will this break existing Filament UI customizations?
- The package is designed to be idempotent and patches theme CSS without conflicts. However, heavily customized Filament views (e.g., sidebar.item or dropdowns) may need validation post-integration. Test in staging first.
- Does Filament Flux support Filament’s pagination features like pageOptions?
- No, Flux replacements drop some Filament-specific features like `pageOptions` in pagination. If your project relies on these, disable the Flux pagination replacement or use workarounds.
- How does this handle modals and action confirmations?
- Flux’s free tier lacks a modal component, so the package relies on Filament’s native modals for actions and confirmations. If your project uses custom modals, ensure they remain compatible with Filament’s system.
- What if my project uses non-Heroicon icons (e.g., Font Awesome or Tabler)?
- The package includes a `HeroiconNormalizer` to handle mixed icon sets, but edge cases may require manual fixes. Test thoroughly if your project relies heavily on non-Heroicon icons.
- Is there a way to preview changes before enabling Flux everywhere?
- Yes, use the `useEverywhere()` flag incrementally to test Flux components in specific areas of your Filament panel. This allows you to opt out problematic fields while adopting others.
- Are there any known conflicts with other Filament plugins?
- Some Filament plugins (e.g., filament-notifications or filament-widgets) may have components like `statsCard` that need validation. Test your plugin stack in a staging environment to identify potential conflicts.