Weave Code
Formtype Bundle Laravel Package
integrated/formtype-bundle
Symfony bundle for defining and managing reusable form types with clean configuration and integration-friendly defaults, helping you build consistent forms faster across your applications.
Integrated FormType Bundle
Frequently asked questions about Formtype Bundle
- Is integrated/formtype-bundle a Laravel package?
- No. It is a Symfony bundle: it uses the -bundle suffix, FormType vocabulary, the Kernel::registerBundles() lifecycle, a DependencyInjection extension, and Twig form themes. Laravel has no bundle concept, so its closest analogues are service providers, FormRequest validation, and Blade components. Treat it as a Symfony dependency, not a Laravel package.
- Can I install integrated/formtype-bundle in a Laravel application?
- Composer can technically require it, but the bundle almost certainly cannot run without FrameworkBundle. There is no Laravel package auto-discovery, no config-publish convention, and no facade layer. It is not a supported or realistic integration path for a Laravel app.
- What does Integrated FormType Bundle actually do?
- It provides a way to define and manage reusable Symfony form types with dependency-injection wiring and integration-friendly defaults. The value, if any, is in domain-encoded type definitions rather than in Laravel-style form handling. Expect thin glue over symfony/form plus Twig form themes.
- Which Laravel and PHP versions does it support?
- Unknown. There is no Packagist metadata, no documented PHP range, and no stated target Symfony major version. Assume PHP 7.x-era syntax and Symfony 3 or 4 constraints until proven otherwise, and assume it will not run on PHP 8.2+ or modern Laravel without patching. Verify composer.json constraints before spending any integration time.
- Is the package actively maintained?
- There is no positive maintenance signal. It has zero stars, zero dependents, is hosted on Bitbucket rather than GitHub, and has no issue history or documentation beyond a restatement of the name. A package with no dependents has no maintenance contract behind it, so adoption is effectively ownership transfer.
- What license is Integrated FormType Bundle released under, and can I fork it?
- License terms are unverified. Before vendoring or forking, confirm the Bitbucket repository is publicly clonable and that its license permits commercial use, modification, and redistribution. If no license file exists, default copyright applies and you cannot legally reuse the code.
- How would I use Symfony forms inside a Laravel application?
- The only credible path is symfony/form as a standalone component, not this bundle. You would supply a validator, renderer, CSRF token manager, and template engine, then rewrite all wiring behind a single adapter interface so the dependency stays isolated to one namespace. Budget a multi-week spike plus permanent carrying cost, and expect a second validation and rendering layer alongside Laravel's own.
- What are the Laravel-native alternatives for consistent, reusable forms?
- Use Blade components with FormRequest validation for standard forms, Filament or Livewire for dynamic and admin-style forms, and Inertia with Vue or React when you need a full-stack SPA. These keep one validation and one rendering layer instead of two. Reimplementing the bundle's type definitions as FormRequests and Blade partials typically costs far less than integrating it.
- How should I evaluate the bundle's source before committing to it?
- Clone the repository and read src/, DependencyInjection/, and Form/Type, which should take one to two hours. Decide whether the real value is domain-encoded type definitions you can reimplement, or genuine dynamic Form behavior worth spiking as a standalone component. Run composer why-not and composer audit after any install attempt, and mirror the repository in case it disappears.
- Is integrated/formtype-bundle safe for production use?
- Technical risk is high because of absent signal: no dependents, no community security review, no issue history, and unverified PHP and Symfony compatibility. Transitive dependencies may be abandoned, and the Bitbucket host adds availability risk. Do not put it in production without a named internal owner, a fork plan, and a documented exit strategy.
Weaver
How can I help you explore Laravel packages today?