Weave Code
Flowbite Bundle Laravel Package
tales-from-a-dev/flowbite-bundle
A Symfony form theme for Flowbite that gives your forms a modern Tailwind-based look out of the box, with light and dark themes, CSS class overrides, and custom types like SwitchType.
A Symfony form theme for Flowbite
Frequently asked questions about Flowbite Bundle
- Is tales-from-a-dev/flowbite-bundle a Laravel package?
- No. It is a Symfony bundle that provides a form theme for Flowbite, registering Twig templates through Symfony's form_themes configuration. It ships no service provider, no Blade views, and no integration with Laravel's Form builder, so it is not a drop-in dependency for a Laravel application.
- Can I use this Flowbite form theme in a Laravel app?
- Not directly. Using it in Laravel would mean porting every Twig template to Blade and re-implementing Symfony's form rendering contract, which is a bespoke fork rather than an integration. For a Laravel stack, treat the repository as a design reference for per-field class maps and error/help markup, and build equivalents with Blade components or an existing Laravel Tailwind form library.
- How do I install flowbite-bundle in a Symfony application?
- Run composer require tales-from-a-dev/flowbite-bundle, then register the bundle in config/bundles.php. Add the theme to your Twig config under form_themes, placed after any base theme so it wins per block without losing Symfony's defaults for uncovered types, and wire Flowbite CSS and JS through your existing asset pipeline such as Webpack Encore or Vite.
- Which PHP and Symfony versions does flowbite-bundle require?
- The package requires PHP 8.1 or newer and Symfony 6.4 or 7.x, along with Twig and the Symfony Form component. If your application is on an older Symfony major or PHP 8.0, the bundle is not installable without changes. Confirm your form theming configuration is compatible before adding it to a production project.
- Which Flowbite version does this Symfony form theme target?
- The README states Flowbite 4.0 or newer, but you should validate that against the actual Flowbite release line you ship. The theme is coupled both to Symfony's form theme API and to Flowbite's class vocabulary, so a version mismatch can still render valid CSS with the wrong visual output. Pin your Flowbite version explicitly and record it in an ADR.
- How do I override the default Flowbite CSS classes in flowbite-bundle?
- The bundle documents a class override mechanism and a class block list, which let you swap design-system classes without editing the shipped Twig templates. Use that mechanism first, before forking templates, and keep your overrides in one place so upgrades stay manageable. Light and dark theme variants are included, so check overrides in both modes.
- What is SwitchType in flowbite-bundle?
- SwitchType is a custom Symfony form type included with the bundle that renders a toggle switch using Flowbite markup. It is intended for boolean-style inputs where a checkbox rendered as a switch fits the UI better than a standard checkbox. Treat it like any custom form type when testing rendering, validation, and error display.
- What happens if a form field type is not covered by the Flowbite theme?
- Symfony form themes fall back to the default theme for any block the Flowbite theme does not define, which can produce inconsistent markup across a form. Review the theme's coverage for choice expanded, collection, file, and error/help blocks before rollout. Also avoid stacking conflicting themes, because the last registered theme wins per block.
- Will Tailwind purge the bundle's form classes in production?
- Tailwind generates classes only from files matched by your content globs, so the bundle's Twig template paths must be included or its classes will be stripped in a production build. Verify your Tailwind configuration covers the vendor templates and rebuild before release. This is a common cause of forms looking unstyled in production but fine in development.
- Is flowbite-bundle safe to depend on in production?
- Adoption signals are low, with roughly 90 stars, no dependents, and a small maintainer organization providing community-only support. The bundle is MIT licensed, so you can fork it, but you should decide in advance who owns that fork and what your patching SLA is. For a Laravel codebase the honest recommendation is not to adopt it as a dependency at all.
Weaver
How can I help you explore Laravel packages today?