- Can I use ite/form-bundle in a Laravel application?
- No. ite/form-bundle is a Symfony 2 bundle that extends the Symfony Form component and ships Symfony DI service definitions, Twig form themes, and an Assetic-era asset pipeline. Laravel has no first-class Form component or bundle/kernel extension model, so there is no seam where this package plugs in. Direct Composer installation will not register a service provider or facade.
- Does ite/form-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 2.x and the PHP 5.3–7.x era, with Twig 1.x and Assetic assumptions. Laravel 10 and 11 require PHP 8.1+ and use Vite, Blade, and a completely different container and asset model. There is no compatibility path without running a second Symfony stack inside Laravel.
- How do I install ite/form-bundle with Composer?
- You can run composer require itedev/form-bundle, but in Laravel it will not auto-register, publish config, or provide routes, views, or assets. The package expects Symfony's bundle registration and kernel extension model. In a Symfony 2 project it would be enabled in AppKernel, but that framework version is end-of-life.
- What PHP and Symfony versions does ite/form-bundle require?
- It is built for Symfony 2.x and the PHP 5.3–7.x era, with Twig 1.x templates and Assetic for asset handling. Those constraints are likely a hard stop against a modern Laravel stack on PHP 8.2+. Confirm the exact composer.json constraints before any spike, but expect incompatibility.
- Is ite/form-bundle actively maintained?
- No. The package has a 0.07 package score, 14 GitHub stars, and zero dependents, which means there is no downstream pressure to fix issues. It targets Symfony 2, which has been end-of-life since 2019. Treat it as an unmaintained reference implementation rather than a dependency.
- What are the best alternatives to ite/form-bundle for Laravel forms?
- For Laravel, use Blade components with typed props, Laravel validation rules and FormRequest preparation hooks, and Vite for assets. Pair that with Alpine.js or Livewire lifecycle hooks for dynamic widgets, and maintained JavaScript libraries such as Select2, Flatpickr, TinyMCE, or FilePond for select, date, WYSIWYG, and upload features. Filament and Livewire ecosystem packages cover many form-building ergonomics if you want a higher-level toolkit.
- Is ite/form-bundle safe to use in production?
- It carries high technical risk. The bundled jQuery plugins from the Symfony 2 era are a recurring source of XSS and prototype-pollution advisories, and there is no patch channel because the package is unmaintained. There is also an architectural risk of producing an inconsistent Laravel/Symfony hybrid that is hard to staff and harder to remove.
- Can I reuse the Select2, datepicker, WYSIWYG, and AJAX upload integrations in Laravel?
- Not directly. The bundle's value-add JS layer is coupled to Symfony form themes, Twig rendering, and Assetic, so reusing it means inheriting Twig, a translation stack, and CSRF/session bridging. The sane path is to reimplement each widget as a small Alpine directive or Livewire hook backed by a maintained modern library. Timebox that work to a sprint and own it in an internal package.
- How do I migrate a Symfony 2 form built with ite/form-bundle to Laravel?
- There is no migration path, only reimplementation. Translate form-type composition into Blade components with typed props, replace data transformers with Laravel validation rules and FormRequest preparation hooks, replace widget wiring with Alpine directives or Livewire lifecycle hooks, and replace Assetic with Vite entry points. Package the result as an internal package such as acme/forms-ui with tests and a version constraint you control.
- What is the license of ite/form-bundle and can I vendor its source?
- Check the repository LICENSE file before doing anything; the README excerpt provided here does not state it. Even if the license is permissive, vendoring source into an internal package creates compliance and long-term maintenance obligations. Given zero dependents and no patch channel, reading the code as a reference for a day is safer than forking it.