- How do I install filament-bladewind in a Laravel app?
- Install it via Composer with composer require jeffersongoncalves/filament-bladewind, then publish any package assets and register the Bladewind integration in your Filament panel provider. Clear application and package caches after installation and verify that your panel loads the Bladewind components correctly. Check the README for the exact publish commands and plugin registration syntax for your Filament version.
- Which Laravel and Filament versions does filament-bladewind support?
- The package targets Laravel applications using Filament and Livewire, but the exact Laravel, Filament, Livewire, and PHP constraints are defined in its composer.json and README. Check those constraints before upgrading, particularly if you use an older Filament line or a newer Livewire release. Validate the combination in staging because version compatibility can vary by package release.
- What does filament-bladewind do to Filament theme CSS?
- It splits the Filament fi-* theme stylesheet per page and builds a rule index so that only the CSS needed for the current page is delivered. Missing rules are streamed to Livewire updates, which helps keep Bladewind-styled components consistent during dynamic interactions. In version 3.0.2 the theme splitting and rule-index work is cached through Laravel's cache store to reduce warm-path cost.
- How does the cache in filament-bladewind 3.0.2 work?
- Version 3.0.2 moves per-request memoization into Laravel's cache store, so theme splitting and rule-index builds can be reused across requests. Cache entries are replaced when the theme content hash changes and when script modification times change. Use a shared cache backend such as Redis or Memcached for multi-node deployments, and clear and warm the cache during deployment.
- Is filament-bladewind safe to use in production?
- It can be production-ready for Filament panels, but the main risk is cache invalidation correctness rather than raw CPU cost. Make sure theme content hashes and script modification times invalidate reliably in your deployment model, especially with Docker builds, symlinked releases, or immutable containers. Validate cache-store availability, key scoping for multi-panel or multi-tenant setups, and warm the cache during deploy before enabling it widely.
- Does filament-bladewind work with Laravel Octane?
- It should work under Laravel Octane as long as the package uses Laravel's cache abstraction and your cache store is shared across workers. Confirm that cache keys are scoped correctly for themes, panels, and tenants so warm entries are not trapped per process. Test Livewire updates and theme switching under Octane in staging, and verify that mtime-based invalidation still behaves correctly in your container or symlink deployment.
- How do I clear or warm the filament-bladewind cache?
- Clear the application cache with php artisan cache:clear and any package-specific cache commands documented in the README, then warm the Bladewind caches during deployment. Because 3.0.2 depends on cache correctness, warming after asset publishing and theme compilation helps avoid cold-start stampedes. Verify panel rendering and Livewire updates after clearing the cache.
- Can I use Bladewind components in Filament resources and forms?
- Yes, the package is intended to let you use Bladewind's Blade components alongside Filament resources, forms, and tables. It handles per-page CSS splitting and streams missing rules to Livewire so Bladewind-styled components remain consistent during dynamic updates. Use it when you want Bladewind's accessible component style without replacing Filament's admin structure.
- What are the alternatives to filament-bladewind?
- Alternatives include using Filament's built-in theme and Blade components, building custom Tailwind-based components, or integrating another UI kit directly into Filament. filament-bladewind is distinctive because it splits the fi-* theme per page and streams missing CSS rules to Livewire updates. Choose it when you specifically want Bladewind components and can validate the cache-based optimization in your deployment.
- Are there breaking changes from earlier 3.x versions of filament-bladewind?
- Release 3.0.2 is a patch release and the notes do not describe schema changes, new services, or breaking API changes, so semver suggests a low-friction upgrade. The main behavioral change is that work moves from per-request memoization to the Laravel cache store, which can affect cache invalidation and deployment warmup. Test the upgrade in staging and confirm cache keys, TTLs, and fallback behavior before rolling it out to production.