Weave Code
Form Bundle Laravel Package
enhavo/form-bundle
A subtree split of Enhavo, an open source PHP CMS built on the fullstack Symfony framework, offering a flexible system for complex data structures with a clean, usable interface. See the main repository for full documentation and details.
[READ-ONLY] EnhavoFormBundle
Frequently asked questions about Form Bundle
- Is enhavo/form-bundle a Laravel package?
- No. enhavo/form-bundle is a Symfony bundle and a read-only subtree split of the Enhavo CMS monorepo, not a Laravel package. It assumes Symfony's Form component, dependency injection container, and Twig form themes rather than Laravel's container, Blade, or Eloquent. Laravel teams should treat it as a Symfony CMS component, not a drop-in Laravel dependency.
- Can I use enhavo/form-bundle in a Laravel application?
- Technically you could try to bridge it, but practically it is not attractive. You would need to run Symfony's DI container and Twig alongside Laravel's container and Blade, or reimplement the bundle's wiring natively and effectively stop using the package. That creates a Symfony-shaped island in a Laravel app and doubles compatibility work for every Laravel or PHP upgrade.
- What Symfony and PHP versions does enhavo/form-bundle support?
- The README does not publish a supported Symfony or PHP version matrix. You must inspect the package's composer.json and source to find its exact require constraints and any hard dependencies on Enhavo core bundles. Treat the constraints as undocumented until you verify them yourself.
- How do I install enhavo/form-bundle with Composer?
- The normal mechanism would be composer require enhavo/form-bundle, but installation alone does not make it usable. The bundle is designed as part of a larger Enhavo CMS adoption, so you also need the required Enhavo bundles, configuration, and Twig form theme setup. For a Laravel project, installation is not recommended.
- Is enhavo/form-bundle safe to use in production?
- It carries high technical risk for a Laravel product: it has 0 stars, 0 dependents, a readme-level maturity signal, and no independent release lifecycle. It is a single-vendor CMS component with no visible external consumers and no fork network to fall back on. Abandonment risk is real, so production use outside Enhavo should be avoided.
- Does enhavo/form-bundle work standalone without the Enhavo CMS?
- That is not documented and is unlikely. The bundle is integration glue around Symfony's Form component for Enhavo's CMS, and it most likely depends on Enhavo's resource, configuration, and admin conventions. You cannot confirm standalone usability from the README; you would have to map the source and composer.json dependencies.
- What are the best Laravel alternatives to enhavo/form-bundle?
- For Laravel, use the framework's native form surface: validation rules, Form Requests, Blade components, and Livewire, Filament, or Inertia for dynamic UI. These cover server-side form definitions, admin-side form configuration, and dynamic form building with first-class Laravel support. They also avoid a two-sided Symfony/Laravel compatibility problem.
- Why is enhavo/form-bundle read-only and where do I report issues?
- The repository is a read-only subtree split of the enhavo/enhavo monorepo, so it has no issue tracker activity or pull-request path of its own. All contributions and bug reports must go through the main Enhavo repository on the maintainers' schedule. That governance model means you cannot patch the package upstream through its own repo.
- Does enhavo/form-bundle support Blade templates or only Twig?
- It is Symfony-native and uses Twig-based form themes, not Blade. There is no documented Blade integration, and the themes and asset pipeline are not described as separable. Using it in Laravel would mean running Twig alongside Blade or rebuilding the rendering layer.
- What should I check before adopting enhavo/form-bundle?
- Inspect composer.json for the exact require set, Symfony and PHP constraints, and whether Enhavo core bundles are hard dependencies. Confirm whether the form bundle is usable standalone or needs Enhavo's resource bundle, metadata configuration, and admin stack. Also check the subtree-split sync cadence, recent maintenance responsiveness, and where consumers file issues.
Weaver
How can I help you explore Laravel packages today?