- What is Filament Jet used for?
- Filament Jet is a Laravel package that adds Laravel Jetstream-style account features to Filament panels. It provides ready-made pages and components for profile management, security settings, API tokens, and team features. It is aimed at developers who want those screens without building custom Filament UI.
- Is Filament Jet production-ready?
- Not by default. The package is at v0.0.2 with only two tagged releases and pre-1.0 versioning, which signals unstable public APIs. It may be reasonable for prototypes or internal admin panels, but production adoption should be gated on dependency compatibility checks, testing, and exact version pinning.
- Does Filament Jet support Laravel 11?
- There is no published support matrix confirming Laravel 11 compatibility. The v0.0.2 release specifically widened framework support up to Laravel 10. Check composer.json constraints for illuminate/*, filament/filament, laravel/jetstream, and PHP before assuming Laravel 11 works.
- Which Filament and Jetstream versions does Filament Jet support?
- The package does not publish a formal support matrix, so composer.json is the source of truth. Validate the constraints for filament/filament, laravel/jetstream if present, illuminate/*, and PHP in your target app. Because it is pre-1.0, pin the exact package version and avoid floating constraints.
- How do I install Filament Jet in a Laravel app?
- The general path is to require artmin96/filament-jet with Composer using an exact version pin, then follow the package README for Filament panel registration and any migrations or config publishing. Install it first in a non-critical Laravel 10 + Filament environment. Do not adopt it without checking dependency constraints and running your own smoke tests.
- Does Filament Jet include teams, profile, security, and API token features?
- Yes, based on its stated scope it provides ready-made Filament pages and components for profile management, security settings, API tokens, and team features. The exact behavior depends on the package version and your Filament/Jetstream configuration. Test team scoping, profile updates, token creation and revocation, and authorization boundaries explicitly.
- How should I test Filament Jet before using it?
- Start with a proof of concept in a non-critical Laravel 10 + Filament app and pin the package version. Exercise authentication, profile updates, team scoping, API token flows, and permission boundaries with feature tests. There is no evidence of automated test coverage for those flows, so your own test suite is essential.
- What are the main risks of adopting Filament Jet?
- The main risks are breaking changes in future 0.0.x releases, Composer dependency conflicts with Filament, Jetstream, Laravel, or PHP, and long-term maintainer continuity. There is also no visible security policy or deep changelog, and auth/team flows touch sensitive session and authorization paths. Plan for periodic dependency and security review and be ready to fork or replace it.
- How is Filament Jet maintained and supported?
- Release history is minimal, with only 0.0.1 and 0.0.2 tagged and a low release cadence. Support appears to be GitHub-issue-driven with no commercial backing evident. Document workarounds internally and treat bus-factor risk as a real operational concern.
- What alternatives to Filament Jet should I consider?
- Alternatives include Filament Breezy for Filament auth/profile scaffolding, Laravel Jetstream or Fortify combined with custom Filament pages, or building the needed profile, security, token, and team screens directly in Filament. Compare maintenance activity, Laravel and Filament version support, and test coverage before choosing. For production, a maintained alternative or a focused custom implementation may be lower risk.