- How do I install filament-flux-pro in a Laravel Filament v5 project?
- Run `composer require jeffersongoncalves/filament-flux-pro` and publish the config with `php artisan vendor:publish --tag=filament-flux-pro-config`. After installation, run `npm run build` and `php artisan view:clear` to compile assets and clear cached views. Ensure you have a valid Flux Pro license before proceeding.
- What Laravel and Filament versions does this package support?
- This package supports Laravel 12/13, Filament v5.x, and PHP 8.2+. It requires Flux Pro v2.13+. Check the compatibility table in the README for exact version mappings. Always pin versions in `composer.json` to avoid conflicts.
- Can I use filament-flux-pro without a Flux Pro license?
- No, this package requires a commercial Flux Pro license because it depends on the proprietary `livewire/flux-pro` package. The wrapper itself is MIT-licensed, but runtime functionality depends on the licensed components. Consider the free `filament-flux` package if licensing is a concern.
- How does `useEverywhere()` work, and will it break my existing Filament fields?
- `useEverywhere()` automatically replaces Filament’s default fields (e.g., `RichEditor`, `DatePicker`) with Flux Pro equivalents. While convenient, it may override custom logic in existing fields. Test thoroughly in a staging environment, and disable auto-binding for critical fields by excluding them in the config.
- Are there any CSS or JavaScript conflicts with existing Filament themes?
- The package patches Tailwind v4 CSS for Flux Pro components to maintain visual consistency with Filament themes. However, if you’re using custom CSS or JavaScript, conflicts may arise. Use Filament’s panel isolation or namespace your styles to avoid collisions. Test in a development environment first.
- Can I use filament-flux-pro in a legacy Filament v4 project?
- No, this package is designed exclusively for Filament v5. If you’re on Filament v4, you’ll need to migrate to Filament v5 first. The package does not support backward compatibility with earlier versions. Plan for a phased migration if upgrading is a concern.
- What are the performance implications of using Flux Pro components?
- Flux Pro components are optimized for reactivity and performance, but some (e.g., `FluxEditor` or `FluxKanban`) may introduce higher initial load times due to their complexity. Benchmark critical components against vanilla Filament equivalents in your staging environment. Use lazy-loading for non-critical widgets.
- How do I handle updates to Flux Pro or filament-flux-pro?
- Monitor the package’s GitHub repository for breaking changes, especially when Flux Pro releases updates. Test updates in a staging environment before deploying to production. If issues arise, roll back by pinning versions in `composer.json` and reverting asset builds. Always back up your database and assets before major updates.
- Are there alternatives to filament-flux-pro for open-source Flux-like components?
- Yes, if you need open-source alternatives, consider packages like `spatie/laravel-medialibrary` for file uploads, `ckeditor/ckeditor5-build-classic` for rich text editing, or `flatpickr/flatpickr` for date pickers. However, these won’t integrate natively with Filament like Flux Pro does. Evaluate tradeoffs in functionality and development effort.
- How do I integrate Flux Pro charts with Eloquent models or Laravel queries?
- Flux Pro charts (e.g., `FluxLineChartWidget`) support Eloquent relationships and Laravel queries out of the box. Pass a query builder instance or model to the chart component, and it will automatically fetch and visualize the data. For complex datasets, preload data in the resource’s `getData()` method to optimize performance.