- What’s the difference between this package and Laravel Jetstream?
- This package replaces Jetstream’s Blade UI with Filament components, offering a modern admin panel experience while keeping Jetstream’s core features (auth, teams, API tokens). It’s ideal if you’re already using or want to adopt Filament for your Laravel project.
- Can I use this in an existing Laravel project with custom auth logic?
- Yes, but you’ll need to manually merge custom auth logic with the package’s traits (e.g., `InteractsWithProfile`). Run `php artisan vendor:publish` to publish migrations and resolve conflicts with existing models or middleware.
- Does this support Laravel 13? What about Filament v4?
- Yes, it’s tested on Laravel 11–13 and Filament v3+. Filament v4.x is supported, but check the changelog for updates like the `registerRoutes` changes in v4.8.0, which may require adjustments.
- How do I enable teams or API tokens without installing everything?
- Use the `--teams` or `--api` flags during installation (e.g., `filament-jetstream:install --teams`). These features are opt-in and won’t bloat your app if unused. Teams require an additional migration (`filament-jetstream-team-migration`).
- Is email verification included by default? What about 2FA?
- Email verification isn’t included by default—you’ll need to customize the registration flow. Two-factor authentication (2FA) is supported but requires publishing its migrations (`filament-two-factor-authentication-migrations`).
- Will this work if I’m not using Filament yet?
- No, this package *requires* Filament v3+ as its UI layer. If you’re not using Filament, consider Laravel Jetstream (Blade-based) or Breeze (minimalist). The learning curve for Filament is low, but evaluate your team’s comfort level first.
- How do I customize user fields (e.g., adding a ‘role’ column)?
- Extend the `User` model and publish the package’s migrations to avoid conflicts. Override Filament’s profile panel by creating a custom resource or modifying the `JetstreamPlugin` configuration in `AppServiceProvider`.
- Are there performance concerns with teams or API tokens?
- Teams and API tokens add complexity, but the package is optimized for typical SaaS/internal tool use cases. For large-scale apps, benchmark database queries (e.g., team memberships) and consider caching strategies for API token lists.
- What if Filament updates break this package?
- The package aims to align with Filament’s API, but breaking changes (e.g., v4.8.0’s route registration) may require updates. Monitor the GitHub repo for patches or contribute fixes. Consider forking if rapid Filament changes are a concern.
- Can I use Passport or Sanctum for API auth with this?
- Yes, the package integrates with Laravel Sanctum (default) or Passport for API tokens. Enable it during installation with `--api`, then use Sanctum’s `HasApiTokens` trait or Passport’s `HasApiTokens` for customization.