Weave Code
Basev4 Laravel Package
filakitphp/basev4
FilakitPHP/BaseV4 is a lightweight Laravel package offering foundational utilities and scaffolding for Filament v4 projects, helping developers streamline admin panel setup and common backend tasks with simple installation.
Base starter kit built on Laravel 13.x and Filament 4.x with a ready-to-use admin panel structure.
Frequently asked questions about Basev4
- What is filakitphp/basev4 and is it a Laravel package or starter kit?
- filakitphp/basev4 is an opinionated Laravel 13.x and Filament 4.x application baseline, not a general-purpose utility library. It provides a starter kit with a ready-to-use admin panel structure and foundational scaffolding for Filament v4 projects. Teams typically use it as a greenfield baseline or reference implementation rather than as a drop-in package for arbitrary Laravel apps.
- Which Laravel and Filament versions does filakitphp/basev4 support?
- The package is built on Laravel 13.x and Filament 4.x, and the 4.14.0 release aligns the baseline with Filament v4.14.0. The release notes referenced here do not state a complete Laravel or PHP runtime matrix, so verify composer.json constraints before adopting it. Confirm compatibility with any Filament plugins already used in your application.
- How do I install filakitphp/basev4 in a new Laravel project?
- Use Composer to require filakitphp/basev4 in a fresh Laravel/Filament project, then follow the repository's scaffolding and setup steps for the admin panel. The context does not list exact publish, migrate, or seed commands, so review the README and generated files before running them. Validate the generated auth, user resource, policies, and login flow in a spike branch first.
- Is filakitphp/basev4 suitable for existing Laravel applications?
- Feasibility is medium for existing applications because 4.14.0 changes user model, user resource, and login wiring while bumping a core Filament dependency. It is a better fit for greenfield Laravel/Filament projects or as a reference implementation than for apps with highly customized auth domains. If you adopt it, diff 4.13.4...4.14.0 and treat the filament-user change as a targeted migration rather than a blind Composer update.
- What changed in filakitphp/basev4 4.14.0 regarding filament-user and authentication?
- Release 4.14.0 moves authentication and user modeling toward filament-user and aligns the baseline with Filament v4.14.0. That is architecturally sensible for Filament-centric applications, but it increases coupling to Filament's auth conventions and can affect downstream scaffolds. No explicit breaking changes or security advisories are called out, but treat the auth-related change as behavior-affecting and test guards, policies, factories, seeders, and social login flows.
- Does filakitphp/basev4 work with PHP 8.4 and what runtime versions are supported?
- CI now runs PHPStan on PHP 8.4, which shows the project is being checked on that runtime. However, the release notes do not state the full supported PHP or Laravel runtime matrix, so CI coverage alone is not a support guarantee. Review the package's Composer constraints and test on your production PHP version before relying on it.
- Can I use filakitphp/basev4 without Filament or with custom Filament plugins?
- It is a poor fit for teams not using Filament because the baseline is built around Laravel 13.x and Filament 4.x admin conventions. For custom Filament plugins, confirm Filament v4.14.0 compatibility with your installed plugins and resources before upgrading. Validate representative plugins in staging because plugin/resource conflicts are a key technical risk.
- How should I test and validate an upgrade from filakitphp/basev4 4.13.4 to 4.14.0?
- Pin the current baseline, capture generated files, review the 4.13.4...4.14.0 diff, and inspect Composer lock changes before upgrading. Upgrade in an isolated branch, keep the pnpm lockfile stable because the bun migration was reverted, and run Composer plus frontend builds with pnpm. Then execute auth/login/resource smoke tests, PHPStan/tests, and staging validation with representative Filament plugins.
- Is filakitphp/basev4 production-ready and what support is available?
- It can be production-ready as a starter baseline for Laravel/Filament teams that budget internal ownership for auth customization and upgrades. Support appears to be community/open-source via GitHub issues and pull requests, with no evidence of a commercial SLA. Maintenance is low-to-medium as a starter baseline but higher if you treat it as a long-lived upstream dependency.
- Are there alternatives to filakitphp/basev4 for Laravel admin panels?
- Alternatives include building directly on Laravel and Filament without a starter kit, using official Filament scaffolding, or adopting a different Laravel admin panel baseline. Choose filakitphp/basev4 when you want an opinionated Laravel 13.x and Filament 4.x starting point with an admin panel structure. Avoid it if your team does not use Filament, has a highly customized user/auth domain, or cannot absorb Filament's release cadence.
Weaver
How can I help you explore Laravel packages today?