Weave Code
Base Laravel Package
filakitphp/base
Filakit Base is the shared foundation for Filakit PHP packages, providing core service providers, utilities, and conventions for Laravel and Filament projects. It helps developers build consistent, extensible admin panels and modules faster.
filakitphp/base is a lightweight foundation package for building Filament PHP applications on Laravel. It bundles the shared scaffolding—service providers, configuration, helpers, and conventions—that Filament projects typically need, so you can skip repetitive setup and start from a consistent, predictable structure.
- Ready-to-use service provider with config publishing
- Common helpers and utilities for Filament resources
- Sensible defaults for panels, navigation, and layouts
- Laravel package discovery with PSR-4 autoloading
- Extensible base classes for custom components
Frequently asked questions about Base
- What is filakitphp/base and is it a Laravel package or a starter kit?
- filakitphp/base is the foundational starter kit for the Filakit ecosystem, built on Laravel and Filament with a ready-to-use admin panel. It provides reusable base classes, traits, and shared utilities rather than being a runtime library you require into an existing app. The technical assessment characterizes release 3.3.56 as a maintenance release focused on dependency bumps, CI standardization, and build tooling changes.
- How do I install filakitphp/base and create a new Filament admin panel?
- Install it as a project scaffold rather than a Composer dependency, typically with composer create-project filakitphp/base, then configure your environment and run the frontend build. Because release 3.3.56 migrated from pnpm to bun, you should install bun and use the documented bun scripts instead of pnpm. Check the repository README for the exact setup and environment commands.
- Which Laravel and Filament versions does filakitphp/base support?
- The overview describes Laravel 13.x with Filament 3.x, while the technical assessment says the evaluated tag tracks Filament v3.3.56 and assumes Laravel 11/12 with PHP 8.3 or 8.4. Because those statements do not fully align, check composer.json in the repository for the authoritative version constraints before installing. Any Filament plugin in your project must also be compatible with the exact Filament tag used by the starter kit.
- Can I add filakitphp/base to an existing Laravel application?
- It is a starter kit and scaffold, not a drop-in runtime library, so it is not designed to be installed into an existing application as a normal Composer package. You can copy its base classes, traits, shared utilities, and Filament panel structure into an existing project, but that requires manual merging and review. Treat that work as a scaffold comparison rather than a package upgrade.
- Why does filakitphp/base use bun instead of pnpm, and do I need to switch?
- Release 3.3.56 migrated the frontend build tooling from pnpm to bun, which changes the lockfile, CI steps, Docker images, and local development documentation. If your pipeline or Dockerfiles invoke pnpm, plan the switch as the primary integration task rather than treating it as an incidental dependency bump. Confirm in the repository whether pnpm remains supported or merely deprecated, and whether a pnpm lockfile is retained for compatibility.
- What is filament-user and is it a required dependency in filakitphp/base?
- A change in this release switches the scaffolded user model, user resource, and login wiring to the filament-user package. That makes filament-user part of the generated scaffold's authentication setup, and the assessment flags it as a new runtime dependency whose release and support posture should be confirmed. Existing forks are affected only if they cherry-pick that commit, but anyone generating a new project from this tag will get it.
- How do I upgrade an existing filakitphp/base fork to version 3.3.56?
- Treat 3.3.56 as a scaffold refresh rather than a drop-in patch. Pin production forks to 3.3.55 until the filament-user and bun changes are validated, then diff composer.json, package.json, lockfiles, GitHub workflows, dependabot.yml, the User model, UserResource, and the login page in a scratch branch. Port the dependency bumps separately from the authentication and tooling changes.
- Is filakitphp/base production-ready, and how should I pin it in Composer?
- It can serve as an admin foundation for production, but pin exact tags and test upgrades rather than assuming patch-level releases are impact-free. The 3.3.x version line mirrors Filament's version, so a patch number does not guarantee that scaffold changes are non-breaking. The 3.3.56 release includes tooling and authentication changes that a patch label might not imply.
- What CI and testing coverage does filakitphp/base include, and does it support PHP 8.4?
- The release includes GitHub Actions workflow standardization, Dependabot configuration, and PHPStan, which now runs on PHP 8.4. That signals PHP 8.4 support but does not prove the full Laravel, Filament, Livewire, and frontend stack is tested on 8.4. Check the workflow files to see which PHP, Laravel, and Filament matrix is actually covered.
- What are alternatives to filakitphp/base for starting a Laravel Filament admin panel?
- Alternatives include the official Laravel Filament starter kits or assembling a Filament panel manually on a fresh Laravel application. Filakit PHP Base is a good fit when you want Filakit's conventions, reusable base classes, and a pre-wired admin structure. If you only need shared traits and utilities as a runtime package, evaluate lighter Laravel packages or copy the relevant classes instead.
Weaver
How can I help you explore Laravel packages today?