- What is mominalzaraa/filament-jetstream used for?
- It is a Laravel starter kit that integrates Jetstream-style features with Filament panels, including team management, profile updates, API tokens, and account settings. It is intended for Laravel applications that already use Filament and want Jetstream-inspired account and team flows in a cohesive admin experience. It does not replace Laravel or Filament; it sits between Filament UI and Jetstream-style actions.
- How do I install filament-jetstream in a Laravel application?
- Install it with Composer using the package name mominalzaraa/filament-jetstream, then follow the repository README for starter-kit setup and Filament panel configuration. Because it is a starter kit rather than a drop-in plugin, expect to configure your panel, authentication, and team features to match your app. Check the package's Composer constraints before installing to confirm compatibility with your Laravel and Filament versions.
- Which Laravel, Filament, Jetstream, and PHP versions are supported?
- The package targets Laravel applications that use Filament panels and Jetstream-style team management. Exact Laravel, Filament, Jetstream, Livewire, and PHP constraints are defined in the package's composer.json and README, so verify those against your application before upgrading. The v2.1.1 release notes do not list new version requirements, but you should still validate against your installed stack.
- Does this package replace Laravel Jetstream?
- No, it is built around Jetstream-inspired flows and integrates them with Filament panels rather than replacing Jetstream or Laravel's authentication stack. It brings team management, profile updates, API tokens, and account settings into a Filament admin experience. Use it when you want Jetstream-style features surfaced through Filament, not as a standalone replacement for Jetstream.
- What changed in filament-jetstream v2.1.1 for team name updates?
- v2.1.1 changes UpdateTeamName so it delegates to the UpdatesTeamNames contract instead of calling $team->update() directly. That restores the expected extension point for applications that publish or bind custom team-name update actions. It also adds integration and regression tests for default and custom contract bindings, though host applications should still verify their own flows.
- Do I need to publish UpdateTeamName or bind UpdatesTeamNames?
- You only need to publish App\Actions\FilamentJetstream\UpdateTeamName or bind a custom UpdatesTeamNames implementation if you want to customize or extend team-name updates. If your app relies on the package default, v2.1.1 should be a low-friction patch. If you have custom bindings, confirm they still resolve and that your action signature matches the contract after upgrading.
- Will upgrading to v2.1.1 break my custom team-name action?
- v2.1.1 is a corrective patch within the v2 line and does not indicate breaking API changes, but it changes runtime behavior for custom actions. Custom UpdateTeamName classes that were previously ignored may now be invoked, which can expose signature, container binding, authorization, validation, or side-effect issues. Review your custom action and test the full team-name update flow after upgrading.
- How should I test the team name update flow after upgrading?
- Add or run a regression test that updates a team name through the Livewire component using both the default and a custom UpdatesTeamNames binding. Verify that authorization, validation, audit logging, and any side effects in your custom action are actually exercised. Also smoke-test the real Filament panel and team settings flow in staging before deploying.
- Is filament-jetstream safe for production use?
- It can be used in production for Laravel apps that already match its Filament and Jetstream assumptions, but assess maintenance activity and Composer constraints before making it a dependency. The v2.1.1 patch is low-to-moderate risk: corrective, but behavior-changing for apps with custom team-name actions. Keep a Composer lock rollback path and verify the package is actively maintained enough for your risk tolerance.
- What are alternatives to filament-jetstream for Filament account and team management?
- Alternatives include using Laravel Jetstream directly, building custom Filament pages and actions for profiles, teams, and API tokens, or using other Filament plugins that cover account settings. Choose filament-jetstream when you specifically want Jetstream-inspired team and account flows inside Filament. If you do not use Jetstream-style teams, a simpler Filament-only setup may be a better fit.