- How do I install Filament Fabricator in a Laravel 13 project?
- Run `composer require z3d0x/filament-fabricator`, then execute `php artisan filament-fabricator:install`. Register the plugin in your `Panel` provider using `FilamentFabricatorPlugin::make()`, and publish assets with `php artisan filament:assets`. The package supports Laravel 13’s new features like Pint and PHP 8.3.
- Does Fabricator work with Filament v3 or v4, or only v5?
- Fabricator supports Filament v3–v5, but v5-specific optimizations (e.g., `getPages()` for routing) are best leveraged in v5. If using v3/v4, check the upgrade guide for compatibility notes, as some v3/v4 methods may be deprecated in future Fabricator releases.
- Can I use custom block classes with PHP 8.3 features like `readonly` properties?
- Yes, Fabricator supports PHP 8.3, including `readonly` properties and new attribute syntax. However, audit your custom block classes to ensure they align with Laravel 13’s stricter parsing, especially if using Laravel’s new Blade directives like `@props`.
- How does Fabricator handle routing in Laravel 13 compared to older versions?
- Fabricator leverages Filament v5’s `getPages()` method for dynamic routing, which integrates seamlessly with Laravel 13’s optimized bootstrap. No breaking changes exist for Laravel 10/11 users, but Laravel 13 projects benefit from improved TTFB and Vite 5.x asset handling.
- Will Fabricator work with Livewire 3.x in Filament v5?
- Yes, Fabricator is optimized for Livewire 3.x in Filament v5. Test custom blocks for Livewire 3.x changes like `wire:ignore.self` or updated event handling. The package’s block-based design remains modular, so most Livewire logic should carry over with minor adjustments.
- Does Fabricator support API-only Laravel 13 projects?
- No, Fabricator requires Blade rendering for its block-based layouts and frontend routing. If your Laravel 13 project is API-only (e.g., using Inertia.js for frontend), consider alternatives like custom Filament resources or standalone page builders.
- How do I migrate from Fabricator 2.x (Filament v3) to 4.x (Filament v5)?
- Follow Fabricator’s upgrade guide for v5-specific changes, such as `PanelServiceProvider` adjustments or Livewire 3.x event handling. Test custom blocks for compatibility with Filament v5’s `getPages()` method and Laravel 13’s new Blade directives. No database schema changes are required.
- Are there performance benefits in Laravel 13 for Fabricator-powered pages?
- Yes, Laravel 13’s optimized bootstrap and Vite 5.x can reduce TTFB for Fabricator pages. Validate caching strategies (e.g., `Cache::rememberForever`) and ensure custom block assets are properly registered in Vite. The package’s modular design minimizes overhead.
- What if I need to customize the PageResource or routing logic?
- Fabricator provides hooks and extendable classes for customizing PageResources and routing. Override methods like `getPages()` in your custom provider or extend the base `PageResource` class. Documentation covers common extensions for layouts and block behavior.
- Are there alternatives to Fabricator for block-based page builders in Filament?
- Alternatives include custom Filament resources with nested relationships or packages like `spatie/laravel-filament-resource-pages`. However, Fabricator uniquely handles routing, layouts, and reusable blocks out-of-the-box, reducing boilerplate. Compare based on your need for Filament v5 integration or Laravel 13 support.