- What is TeamKit v5 and what does it add to a Laravel application?
- TeamKit v5 is a Laravel 13 starter kit, not a drop-in runtime library, that scaffolds team-aware authentication and a Filament 5 admin panel. It provides the structure for teams, memberships, roles, and invitations so you can build multi-user, team-based features faster. Because it is consumed as a template or create-project base, you generate an application from it rather than requiring it as a production dependency.
- Which Laravel and Filament versions does teamkitv5 require?
- The kit targets Laravel 13.x and Filament 5.x. Version 5.9.0 bumps Filament to 5.9.0, so it is only adoptable if your downstream work is already on the Filament 5 major line. If any part of your stack is pinned to Filament 4, this release is not a fit and should wait until the rest of the stack catches up.
- How do I install jeffersongoncalves/teamkitv5 for a new project?
- TeamKit is intended to be consumed as a starter kit, typically through a composer create-project-style flow or by cloning the repository as a template. Before relying on that in an automated scaffolding pipeline, confirm whether the new user and admin packages introduced in 5.9.0 are published on Packagist with stable tags or are configured as path or VCS repositories. If they are path repositories, a plain create-project will need manual repository configuration first.
- Is TeamKit v5 a runtime package or a starter kit I scaffold from?
- It is an application scaffold and starter kit, not a runtime library you install into an existing app. That means integration is really a fork-and-generate event, and each upstream release becomes a manual rebase against your generated code. Plan for diff review rather than a simple composer update.
- What changed in TeamKit v5.9.0?
- 5.9.0 is a maintenance release with two payloads: routine dependency hygiene, including Filament 5.9.0 and a Vite patch bump, plus one architectural change. PR #152 moves the User model, Filament resources, and login flow into separate user and admin packages, making the starter kit a thin composition layer over internal packages. CI workflow changes in the same release do not affect runtime behavior.
- Does upgrading from 5.8.x to 5.9.0 break App\Models\User?
- Potentially yes. The 5.9.0 change relocates the auth model and login flow behind package namespaces, so code that references App\Models\User or the previously in-app Filament resource classes may need namespace rewrites. The release is a minor version bump but behaves like a breaking change for anyone who already generated an app from 5.8.x. Treat it as a structural migration: pin 5.8.4 as a baseline, build a scratch 5.9.0 app, and diff the auth surface.
- Are the new user and admin packages published on Packagist with stable tags?
- That is the key feasibility question and should be verified before adoption. The assessment notes that if these packages are wired as path or VCS repositories, the starter kit cannot be consumed through a normal composer create-project without manual repository configuration, which is a hard blocker for an automated scaffolding pipeline. Check whether they are semver-tagged and versioned in lockstep with the starter kit.
- Can I use TeamKit v5 for a headless API without Filament?
- TeamKit v5 is built around a Filament 5 admin panel and Livewire-driven UI, so it is a strong fit for an internal tool or admin-panel baseline and a poor fit for a headless API skeleton. Auth and model ownership now route through opinionated user and admin packages, which adds coupling you would have to unwind. If you need a headless API, start from a leaner Laravel base and add team logic yourself.
- How do I test teams, roles, and invitations in a TeamKit v5 app?
- Because TeamKit is a scaffold, you test the generated application with Laravel's normal testing tools rather than testing the kit as a dependency. The repository does standardize test and changelog workflows in CI, which gives you a consistent baseline to extend. Add feature tests for membership rules, role checks, and invitation acceptance, and use Livewire and Filament test helpers for panel behavior.
- Is TeamKit v5 production ready and how is it maintained?
- It is a usable Laravel scaffold, but production readiness depends on your own review of the generated app, especially after the 5.9.0 package split. Maintenance is concentrated in a single maintainer across what is now three packages, so the support window for the 5.8.x line is a real question to ask before standardizing on it. The CI changes also enable auto-merge for Dependabot GitHub Actions minor and patch updates, which means dependency churn will accumulate faster with less human review, so treat it as a supply-chain governance concern.