- What is awcodes/filament-installer used for?
- awcodes/filament-installer is a Composer plugin that scaffolds a Filament panel in a Laravel application. It provides an interactive install flow that generates the panel provider and supporting files so you can boot a Filament admin area with less boilerplate. It is a build-time installer, not a runtime package.
- How do I install awcodes/filament-installer in a Laravel app?
- Require it as a dev dependency with composer require awcodes/filament-installer --dev, then run the installer command exposed by the package. Because it is a Composer plugin, Composer 2.2 and later will ask you to allow the plugin before it can execute. Confirm the exact artisan command in the package README for your Filament major.
- Which Laravel and Filament versions does awcodes/filament-installer support?
- The final release was published on 2022-10-19 and targets the Filament v2 and Laravel 9 era. It does not declare support for modern Filament v3 or v4, or for current Laravel releases. Treat it as a legacy-stack tool rather than a current baseline.
- Does awcodes/filament-installer work with Filament v3 or v4?
- No, it is not a safe fit for Filament v3 or v4. The generated provider and config reflect older Filament conventions, and dependency resolution is likely to fail or produce stale scaffolding. Use the first-party php artisan filament:install --panels flow for modern versions.
- How is awcodes/filament-installer different from php artisan filament:install --panels?
- Filament's first-party filament:install --panels and panel-generation commands now cover the same bootstrap job. awcodes/filament-installer duplicates that capability with an older, third-party installer. Adopting it adds dependency and Composer plugin governance for little residual benefit.
- Is awcodes/filament-installer maintained and safe for production?
- It is not actively maintained: there has been no release in over two years, it has a single maintainer, and there is no documented security-response path. With 14 stars and 0 dependents, there is almost no ecosystem validation. For production use, the safer choice is first-party Filament tooling or an internally owned starter template.
- Can I run awcodes/filament-installer non-interactively in CI?
- The installer is interactive by design, which is hostile to CI, containers, and reproducible onboarding. The evaluation treats it as developer-machine-only unless you can drive the prompts non-interactively and capture the generated diff. For automated provisioning, generate a starter template or use first-party commands instead.
- What files does awcodes/filament-installer generate?
- It generates a Filament panel provider and published config or assets, plus the supporting directory structure needed for a panel. The output is plain Laravel PHP scaffolding that you could hand-write or copy into a starter template. Review the generated provider against current Filament conventions before committing it.
- How do I test a Filament panel generated by awcodes/filament-installer?
- Because the output is ordinary PHP, test it by booting the app and hitting the panel route or running a feature test that asserts the panel is registered. Diff the generated provider and config against first-party scaffolding to catch stale conventions. Do not rely on the installer itself in CI.
- What are alternatives to awcodes/filament-installer for scaffolding Filament panels?
- Use php artisan filament:install --panels or php artisan make:filament-panel for current Filament versions. For repeatable projects, keep a vetted starter template or internal scaffold command. Hand-writing the provider is also viable and avoids a third-party Composer plugin.