- Is mindy/form-bundle a Laravel package?
- No. mindy/form-bundle is a Symfony bundle built for the MindyPHP framework, not a Laravel package. It relies on kernel bundle registration, bundle-class service wiring, and Twig helpers, none of which have a native Laravel equivalent. There is no documented Laravel adapter, so treating it as a Composer drop-in for Laravel will not work.
- How do I install mindy/form-bundle with Composer?
- You would install it with composer require mindy/form-bundle, but only inside an environment that supports Symfony bundles and the MindyPHP container conventions. In a Laravel project there is no supported installation path because no service provider, facade, or config bridge ships with the package. Expect to build and own any integration layer yourself.
- Which Laravel versions does mindy/form-bundle support?
- None are officially supported. The package targets Symfony and MindyPHP conventions, and its Symfony component constraints may not intersect with the symfony/* versions pinned by your Laravel release. A routine Laravel upgrade can therefore orphan the bundle even if you get it working initially.
- Can I use mindy/form-bundle in a Laravel 10 or 11 application?
- Only through a hand-built bridge that runs symfony/form and its dependencies behind an isolated container, which is a deliberate architectural commitment rather than a simple install-and-configure step. There are no reference implementations or dependents to de-risk that work. Most teams are better served by Laravel's FormRequest, Validator, Blade components, Livewire, or Filament.
- What does mindy/form-bundle actually do?
- It packages reusable form field definitions, consistent rendering and handling, and submission processing so you avoid repetitive boilerplate. Functionally it wraps symfony/form, and likely symfony/validator plus the Twig bridge, with defaults and reusable form types. The value is in its form-definition patterns, not in Laravel-specific functionality.
- Is mindy/form-bundle maintained and safe for production?
- The signals are weak: about one star, zero dependents, an overall score near 0.005, no visible release cadence, and no CI indicator. Assume it is abandoned until proven otherwise. Because forms sit directly on the untrusted-input boundary, an unmaintained validation and rendering dependency is a security-relevant liability that needs internal code review and a named owner.
- What are the alternatives to mindy/form-bundle for Laravel developers?
- Laravel's first-party stack already covers the same ground: FormRequest and the Validator for input handling, Blade components or Livewire for dynamic forms, and Filament for admin and schema-driven UIs. If you specifically need server-driven dynamic forms, evaluate maintained JSON-schema renderers or symfony/form used directly behind an owned bridge. Use mindy/form-bundle as design input rather than a runtime dependency.
- Does mindy/form-bundle have tests and a release history?
- There is no visible CI signal, no tags indicated, and no documented release cadence. Before relying on it, check the repository for a test suite, tagged releases, and commit history beyond a single commit. Absent that evidence, plan as if the code is a frozen snapshot you would have to fork and maintain.
- How do I migrate from mindy/form-bundle to Laravel's native form tools?
- The recommended path is reference-only adoption: read the source for its field schema and UX patterns, then rebuild on Laravel primitives. Use FormRequest for validation, Blade or Livewire for rendering, and config-driven schema for field metadata. This avoids inheriting Symfony version drift and MindyPHP container assumptions.
- What are the technical risks of using mindy/form-bundle in a Laravel stack?
- The dominant risk is maintenance and adoption: near-zero usage, no release cadence, and no CI signal. The most likely concrete breakage is version drift, since Laravel pins its own symfony/* component versions and routine upgrades can orphan the bundle. A secondary risk is hidden lock-in to MindyPHP container and Twig assumptions if the bundle is not genuinely standalone.