Weave Code
Basev3 Laravel Package
filakitphp/basev3
filakitphp/basev3 is a foundational Laravel package for Filament v3 projects, offering reusable base classes, configuration, and utilities that streamline admin panel setup, CRUD development, and common scaffolding so teams can build consistent applications faster.
Base starter kit built on Laravel 13.x and Filament 3.x with a ready-to-use admin panel structure.
Frequently asked questions about Basev3
- What is filakitphp/basev3?
- filakitphp/basev3 is a starter kit and base scaffold built on Laravel 13.x and Filament 3.x, shipping reusable base classes, configuration, and utilities for admin panels and CRUD development. It is not a distributable library with a stable public API, so integration means generating a project from it and owning the resulting code. That distinction matters because there is no composer update upgrade path for it.
- How do I install filakitphp/basev3 in a new project?
- You scaffold a project from the repository rather than pulling it in as a runtime dependency. Clone or generate from the specific release you want, run composer install, then complete the normal Laravel setup (env file, app key, migrations, storage link) plus the Filament publish and install commands. Commit the upstream tag or SHA immediately so you can audit and diff against future releases.
- Which Laravel and Filament versions does filakitphp/basev3 support?
- The kit targets Laravel 13.x and Filament 3.x, with the current release pinning Filament 3.3.56. PHP 8.4 appears in CI for static analysis, but passing PHPStan is not the same as declared runtime support. Check the generated composer.json require constraints against your own platform baseline before assuming 8.4 is supported.
- Can I upgrade filakitphp/basev3 with composer update?
- No. Because basev3 is a scaffold and not a versioned dependency, once generated the code is yours and there is no composer update path. Upstream releases are reference material and diff candidates, not automatic dependency bumps. Plan upgrades as manual merges or selective cherry-picks instead of routine composer commands.
- Is upgrading basev3 from 3.3.55 to 3.3.56 safe?
- The 3.3.56 bump is not purely cosmetic: PR #92 swaps the user model, Filament resource, and login to filament-user, and PR #93 moves asset tooling from pnpm to bun. Land PR #92 as its own isolated pull request, separate from the dependency churn, and read the actual 3.3.55 to 3.3.56 diff instead of working from release notes alone. Verify the Filament 3.3.56 pin against the filament-user version constraint before anything else.
- What does the filament-user change in basev3 break?
- It replaces the default User model, the Filament user resource, and the login flow, which is the highest blast radius area in any Laravel application. You need to inventory every touch point: the User model, panel provider authGuard, login page, policies, factories, seeders, and feature tests. Spike the swap on a branch and validate it in staging before merging.
- Does filakitphp/basev3 require bun instead of pnpm?
- Recent releases switch the frontend build tooling from pnpm to bun, which invalidates pnpm-lock.yaml and affects any Dockerfile or CI pipeline that shells out to pnpm. You can keep pnpm locally if that is the faster path, because the choice is decoupled from the PHP side. Just confirm bun, or an accepted workaround, is available in your build images and CI runners.
- Is PHP 8.4 supported by filakitphp/basev3?
- PHP 8.4 shows up in CI through PR #91, which runs PHPStan on 8.4. That signals static analysis coverage, not a declared runtime support contract. Read the composer.json require block yourself and confirm it against your platform baseline before planning a production deployment on 8.4.
- How should I test a basev3 admin panel before going to production?
- Validate in staging rather than trusting a green build: run filament:assets and filament:optimize, then do a config and view republish check and confirm the result with php artisan about. Filament patch bumps sometimes require republishing assets or views, so treat every patch as a possible publish step. Pair that with feature tests covering login and authorization, especially after the filament-user swap.
- Should I use filakitphp/basev3 for production, and what are the alternatives?
- It fits well for a greenfield internal back-office or admin panel where you can own the code, since bootstrapping to a working panel takes days rather than weeks. It fits poorly if you need a versioned, supportable dependency, so the recommended model is scaffold-once and own-the-code, or a vendored fork with a standing quarterly merge slot if you intend to contribute back. Alternatives include the official Filament starter kits, plain Laravel plus Filament, or your own internal template, and you should also weigh maintainer concentration and the volume of auto-merged dependabot updates as an ongoing supply-chain review cost.
Weaver
How can I help you explore Laravel packages today?