Weave Code
Daisyui Form Bundle Laravel Package
islesurlasorguetourisme/daisyui-form-bundle
A Laravel package that bundles DaisyUI-styled form components, helping you build clean, consistent forms with ready-to-use Blade components and configurable fields for faster integration into your views.
A Symfony form theme bundle that provides seamless DaisyUI integration for automatically generated forms
Frequently asked questions about Daisyui Form Bundle
- Does this package work with Laravel, or is it Symfony only?
- It is a Symfony form theme bundle, not a Laravel package. It ships Twig templates that hook into Symfony's Form component theming API (twig.form_themes) and emit DaisyUI/Tailwind classes. Laravel has no Symfony Form component or form-theme abstraction, so the bundle cannot be installed as a working dependency in a Laravel app. The realistic use in a Laravel codebase is as a reference: copy the class mappings and markup conventions into your own Blade components.
- How do I install and enable the bundle in a Symfony application?
- Install it with Composer using the vendor name islesurlasorguetourisme/daisyui-form-bundle, then register the bundle in config/bundles.php. After that you activate the theme either globally via the twig.form_themes config key or per form in a template with the form_theme tag. There is no service container wiring, persistence, or runtime asset pipeline to configure — it is presentation-layer templates only.
- Which Symfony and Twig versions are supported?
- The package targets Symfony 6 and 7 with Twig 3, based on its use of the current form theme extension point. The repository does not publish a detailed compatibility matrix or CI matrix in the material available, so verify the constraint before committing. Run composer why-not against your pinned framework version rather than assuming a constraint resolves.
- Should I register the theme globally or per form?
- Start with per-form scoping using form_theme inside the individual template, not the global twig.form_themes config. That keeps rollback to a one-line revert instead of a deploy and limits blast radius if markup regresses. Only promote to the global theme once a pilot form has passed visual and accessibility review.
- Why do my Symfony forms render unstyled after installing this bundle?
- DaisyUI classes are purged by Tailwind unless the bundle's template directory is included in your Tailwind content globs. This is the most common 'it installed but looks broken' failure with form theme packages. Add the bundle's templates path to the content array and rebuild your CSS.
- Which DaisyUI version does it target, and will utility class renames break it?
- DaisyUI renames component classes across majors — input-bordered became input in newer releases — so output can degrade silently if the theme emits classes from a different major than the one compiled into your CSS. There is no documented version pin in the package metadata, so check the templates for the class conventions you rely on. Pin your DaisyUI major explicitly and review the emitted markup after any DaisyUI upgrade.
- Will this form theme conflict with Bootstrap or Foundation form themes?
- Possibly. It is not documented whether the bundle extends Symfony's base form theme or fully overrides the field blocks; full overrides are the usual cause of conflicts when two themes are registered. Confirm the behaviour before enabling it alongside another theme, and avoid registering two themes globally for the same form. Per-form scoping makes it easy to isolate which theme applies.
- Is there a test suite or golden HTML fixtures I can rely on?
- No test suite or fixture set is visible in the repository, and the project has zero stars and zero dependents. That means there is no production evidence or third-party bug report trail to lean on. If you adopt it, generate your own golden HTML snapshots for representative field types — text, select, radio/choice, file, collection, and error states — so regressions become diffable.
- Who maintains this bundle and what is the abandonment risk?
- It is published by a regional tourism board rather than a package vendor, with no release cadence signal and no dependent projects. Abandonment risk is material, and Symfony form theme markup shifts across framework majors, so an unmaintained theme can fall behind quickly. Check the license and contribution terms first, and only adopt it if forking or vendoring the templates internally stays clean.
- What is the best alternative for using DaisyUI form styles in a Laravel app?
- Build Blade components that render the same DaisyUI class conventions — label, input, select, textarea, checkbox, and error blocks — and own them internally. Pulling symfony/form and Twig into a Laravel service just to consume a template set is not a defensible trade. Treat this bundle as a reference implementation for markup and class mappings rather than a dependency.
Weaver
How can I help you explore Laravel packages today?