- Is insitaction/easyadmin-fields-bundle a Laravel package?
- No. It is a Symfony bundle built on EasyAdminBundle and ships Twig templates, Symfony DI configuration, and field classes that depend on Symfony's HTTP kernel. There is no Laravel service provider, Facade, or adapter surface, so a Laravel-only stack should treat this evaluation as not applicable. In Laravel, the functional equivalents are Filament, Nova, or Backpack.
- How do I install and register this bundle in a Symfony app?
- Install with composer require insitaction/easyadmin-fields-bundle, then enable the bundle in config/bundles.php and import any optional bundle configuration. After that, reference the provided field types inside your CRUD controller's configureFields() method. EasyAdminBundle must already be installed and configured, because the package extends it rather than providing its own admin generator. There is no Laravel installation path.
- Which EasyAdmin and Symfony versions does this bundle support?
- The declared constraints live in the package's composer.json, so audit that file first for the EasyAdmin major, Symfony, and PHP versions. The last release was February 2024, which suggests it targets the EasyAdmin 4.x era and may lag behind later majors or Symfony 7 changes. Pin the bundle against your exact EasyAdmin and Symfony versions in a throwaway branch before any commitment, because version constraints are the most likely cause of failure.
- What field types and widgets does this bundle add to EasyAdmin?
- The bundle adds reusable custom field types and Twig rendering helpers that make EasyAdmin CRUD forms richer with less hand-written template code. Its value is concentrated in admin-UI convenience rather than infrastructure, and it does not touch domain logic, persistence, or authentication. Verify whether the helpers are generic or project-specific by checking for hardcoded routes, entity assumptions, or translations.
- Can I use this package with Laravel or Filament?
- No. This is a Symfony bundle and is explicitly incompatible with Laravel's Blade, Eloquent, and Filament or Nova conventions. Wrapping a Symfony field renderer inside Laravel is more work than reimplementing the field as a Filament or Nova component. Use the Laravel-native equivalents instead.
- What is the dependency footprint and does it require Doctrine or Webpack Encore?
- Plan for PHP 8.x, Symfony 6 or 7, EasyAdmin 4.x, Twig, and typically Doctrine ORM, since EasyAdmin CRUD controllers usually rely on Doctrine. Also check composer.json for transitive dependencies such as frontend assets or Encore/Webpack tooling. If EasyAdmin is absent, adopting this bundle means adopting EasyAdmin, Symfony, Twig, and Doctrine as well.
- Is this package production-ready and actively maintained?
- Code risk is low, but stewardship risk is high. Signals are thin: around 19 stars, zero dependents, an opportunity score near 16.76, and a last release in February 2024, which reads as an agency-internal utility published on a best-effort basis. With no external production validation, assume you own the package once you depend on it and budget for reactive fixes.
- How should I test or spike this bundle before committing?
- Run a sandbox spike on one low-traffic admin CRUD controller over one or two sprints. Pin your EasyAdmin and Symfony versions in a throwaway branch, substitute a couple of ad-hoc field templates with the bundle's fields, and measure actual time saved versus hand-rolled Twig. Document a fallback to native EasyAdmin fields before deciding to adopt.
- What are the alternatives to this bundle for admin panels?
- For Symfony, the primary alternative is native EasyAdmin fields plus your own Twig templates. For Laravel teams, the equivalents are Filament, Nova, and Backpack, which fit Blade and Eloquent conventions. If the bundle is useful but under-maintained, forking it under your own organization is a practical alternative to depending on upstream.
- Should we fork this package and what is the upgrade policy?
- Forking is the realistic steady state if the sandbox spike succeeds. Treat the fork as an internal package, budget roughly one patch cycle per EasyAdmin major upgrade plus reactive fixes for Twig template conflicts, and write an upgrade runbook. Before forking, confirm the maintainer's position on fork-and-own and whether any support arrangement exists.