Weave Code
Bs Select Bundle Laravel Package
axiolab/bs-select-bundle
A Symfony bundle that integrates Bootstrap Select into your forms, adding a ready-made form type and Twig rendering for searchable, styled dropdowns with minimal configuration.
Override symfony choice type implementing bootstrap-select js plugin
Frequently asked questions about Bs Select Bundle
- Is axiolab/bs-select-bundle compatible with Laravel 10 or 11?
- No. It is a Symfony bundle, not a Laravel package, and Laravel has no Form component, Twig renderer, or bundle kernel for it to hook into. There is no supported integration path; adopting it in Laravel would mean rewriting its form widget and JavaScript initialiser as first-party code.
- How do I install axiolab/bs-select-bundle in a Symfony application?
- Require it with Composer, register the bundle class in config/bundles.php, and install the bootstrap-select assets with the assets:install command or a Flex recipe. You then apply the bundle's form theme so the choice widget renders with the plugin markup. There is no Laravel service provider or config file to publish.
- What configuration does the bundle need for the Bootstrap Select form type?
- You register the bundle and its DI extension so the form type extension is available to Symfony's Form component, then add the Twig form theme to your twig.yaml or form configuration. The bundle expects bootstrap-select's CSS and JS to be present on the page. Because it publishes no documented options, treat any behaviour changes as a vendored fork edit rather than configuration.
- Which Symfony versions does this bundle support?
- There is no published compatibility matrix or release tag set, and the code appears to target Symfony 3/4-era APIs. The choice_widget_collapsed form theme block signature has changed across Symfony 5, 6, and 7, so rendering must be verified on your exact version. Test the form theme in a real application before committing to it.
- What does axiolab/bs-select-bundle actually do?
- It overrides Symfony's choice form type to output the markup expected by the bootstrap-select jQuery plugin. The bundle supplies a ready-made form type and Twig rendering so dropdowns become searchable, styled selects with minimal setup. The substance is a form widget override plus a JavaScript initialiser, not a large library.
- Do I need jQuery and Bootstrap to use this bundle?
- Yes. bootstrap-select is a jQuery plugin and depends on a Bootstrap 3/4 stylesheet contract for its styling. If jQuery is not already a first-class front-end dependency, this package introduces it. That is a significant constraint for modern asset bundler and vanilla-JS stacks.
- Can I use bs-select-bundle with Bootstrap 5 or Tailwind?
- Not cleanly. Bootstrap 5 dropped the jQuery dependency that bootstrap-select and this bundle rely on, and Tailwind has no matching markup contract. You would be maintaining a compatibility layer yourself. For Bootstrap 5 or Tailwind projects, a native select enhanced with Tom Select or Choices.js is a better fit.
- How should I test forms that use this bundle?
- Test at two levels: a Symfony form test asserting the choice type renders the expected data attributes, and a browser or JavaScript test confirming bootstrap-select initialises on the rendered markup. Because the bundle has no CI or test suite of its own, you own that coverage. Pin the dependency and re-run the rendering test when upgrading Symfony.
- Is axiolab/bs-select-bundle maintained and safe for production?
- The adoption signal is effectively zero: no stars, no dependents, no Packagist CI or release metadata, and a single maintainer. There is no security advisory channel or CVE tracking, and the repository could disappear without a mirror. For production, vendor-fork it under your own VCS with a named owner, or reimplement the widget.
- What are the alternatives for Laravel developers who want searchable select dropdowns?
- Use a Blade component and a modern vanilla-JS library such as Tom Select or Choices.js, loaded through Vite. That covers searchable, multi-select, and live-filter behaviour without a framework coupling or jQuery. Reimplementing the equivalent of this bundle in Laravel is roughly 100 to 200 lines and one to three engineer-days.
Weaver
How can I help you explore Laravel packages today?