- Is firano/form-bundle a Laravel package or a Symfony bundle?
- firano/form-bundle is a Symfony bundle, not a Laravel package. The repository describes it as NeutronFormBundle, and the -bundle suffix follows Symfony's naming convention. It relies on Symfony primitives such as the HTTP kernel, dependency-injection container, event dispatcher, and symfony/form component. Laravel does not provide those primitives, and there is no service provider, facade, config publishing, or Blade view layer.
- Can I install firano/form-bundle in a Laravel app with Composer?
- Composer may install the package, but that does not make it usable as a Laravel form package. There is no Laravel service provider or auto-discovery integration, so the bundle's services and kernel events would not be registered. A working integration would require a bespoke compatibility bridge that your team would own indefinitely. For a package with no observable adoption, that is usually not a defensible trade.
- How do you install and configure firano/form-bundle?
- In a Symfony application you would typically register the bundle in bundles.php or AppKernel and configure it under its bundle config key, then define form types and rendering templates. The package assumes Symfony's form and templating stack rather than Laravel's Blade and validation layers. Laravel has no standard installation path for this bundle because there is no service provider, facade, or publishable configuration. Any Laravel use would be custom glue code rather than normal package installation.
- Which Laravel and PHP versions are supported by firano/form-bundle?
- No Laravel version support is declared because this is not a Laravel package. You must inspect composer.json for the PHP and symfony/* constraints before spending evaluation time. The firano namespace is associated with mid-2010s Symfony bundles, so PHP 5.x or 7.x-era constraints are plausible. There is no evidence that it is tested against currently supported PHP versions such as 8.2 and above.
- Does firano/form-bundle really work without JavaScript?
- The no-JavaScript claim should be verified rather than assumed. On inspection, it most likely means the package ships its own JavaScript and AJAX endpoints rather than rendering truly JS-free interfaces. That distinction matters because package-owned endpoints and inline scripts become both attack surface and upgrade blockers. Review the bundled JS, Twig theme blocks, and any JSON contracts before relying on the claim.
- How does validation and data binding work in firano/form-bundle?
- Validation and binding are built on Symfony's form component, using form types, constraints, and request-to-form mapping. Laravel's equivalent behavior comes from Form Requests, the Validator service, and Blade or Livewire components. You cannot reuse the Symfony form wiring directly in Laravel without a bridge. In practice you would extract the validation semantics and reimplement them with Laravel-native validation.
- Is firano/form-bundle safe to use in production?
- Security is unknown for this package. It has zero stars, zero dependents, and no observable external review, while form packages sit directly on the untrusted-input boundary. Concerns include mass assignment, CSRF handling, and autocomplete or AJAX endpoints owned by the package. Check for advisories or CVEs against the full transitive dependency tree before considering any use.
- Is firano/form-bundle actively maintained?
- There is no evidence of active maintenance. The project shows zero dependents and no issue traffic, and the firano namespace is associated with mid-2010s Symfony bundles. You should check the last commit date, last release tag, and last issue response. It is also unclear whether a test suite exists or whether CI passes on supported PHP versions, and the bus factor appears to be one.
- What are the best Laravel alternatives to firano/form-bundle?
- Use Livewire for reactive forms without hand-written JavaScript, or Filament Forms for admin and RIA-style form scaffolding with validation and layout. Use Laravel Form Requests plus Blade components for static server-rendered forms with strong validation and no reactivity. Inertia with Vue or React is an option only if your team is already SPA-oriented and accepts JavaScript. Each alternative is actively maintained and has a large install base in the Laravel ecosystem.
- How should I migrate from firano/form-bundle to Laravel?
- Reframe the work as replacement rather than integration. Extract the behavioral specification from the repository, including field types, conditional visibility rules, validation semantics, and autocomplete payload conventions, then reimplement that behavior natively in Laravel. The MIT license makes code reuse as reference legally clean, but do not build a permanent bridge for an unmaintained upstream. Capability-level migration to Livewire, Filament Forms, or Blade components is the defensible path.