- Does bolyfci/livewire-multiselect work with Livewire 3 and Laravel 11?
- Probably not without changes. The last release was February 2021, which places it in the Livewire 2 and Laravel 8 era, and Livewire 3 rewrote its JavaScript layer, Alpine integration, wire:model semantics, and component registration. A 2021 component is unlikely to run unmodified on a current stack. If you need Livewire 3, plan for a fork-and-port rather than a straight composer require.
- How do I install bolyfci/livewire-multiselect in a Laravel app?
- Install it with composer require bolyfci/livewire-multiselect, then publish the config, views, and assets with vendor:publish. On Laravel 5.5 and later the service provider is auto-discovered, so no manual registration is needed. After publishing, drop the component into any Blade form and bind it to a Livewire property with wire:model. Pin your Livewire constraint explicitly in composer.json before merging.
- What Laravel and Livewire versions does this multiselect package support?
- The package dates to the Livewire 2 and Laravel 8 generation, based on its February 2021 last release. There is no published evidence of Livewire 3 or Laravel 10/11 compatibility. Validate it against your app's installed Livewire version in a throwaway branch before committing.
- Is bolyfci/livewire-multiselect still maintained?
- No meaningful maintenance is evident: the last release was February 2021, the repository has around 19 stars, and there are no known dependents. Bus factor is effectively one, so assume zero upstream responsiveness for bug fixes or Livewire compatibility patches. If you adopt it, budget to own the code.
- Why does the Composer name bolyfci/livewire-multiselect differ from the GitHub owner ahmedabdel3al?
- The mismatch usually indicates a fork or a namespace transfer rather than the canonical upstream. That creates provenance ambiguity, because it is unclear whether this copy is orphaned or whether a more active original exists elsewhere. Search Packagist and GitHub for the original project before forking, and confirm which repository you would actually maintain.
- Does it support async or AJAX option loading for large option sets?
- Nothing in the package description suggests lazy loading, and as a server-rendered component its option lists scale linearly with the option set. Large reference tables will degrade unless you verify AJAX or paginated search support in the source. Read the Blade view and component class directly, since the JS surface matters more than the PHP here.
- How do I bind the multiselect to a Livewire property and validate the selected values?
- Bind a selected-values array to a wire:model property, then apply standard Laravel validation rules such as array and exists against that property. The package serializes selections back through Livewire's normal request cycle, so validation should flow through the usual Livewire validation hooks. Confirm in the source that it does not bypass Livewire's request validation, and check that selected labels are escaped rather than rendered as raw HTML.
- Does this package require an npm build step or bundle compiled assets?
- It almost certainly wraps a third-party JavaScript multiselect library, either as a compiled vendor asset or through an npm build step. Check the published assets and composer.json to see which applies in your install. Then verify that vendor:publish and your production build leave the assets fresh rather than silently stale.
- What is the accessibility story for this Livewire multiselect component?
- Accessibility is not documented, and the wrapped JS library's own age makes keyboard navigation and ARIA support uncertain. Before adopting, test keyboard-only operation, focus handling, and screen-reader announcements against your compliance bar. If you have a strict accessibility budget, plan to wrap or replace the front-end layer.
- Should I use this package or build my own multiselect for Livewire?
- Adopt it only if your app is on Laravel 8 or 9 with Livewire 2, or if you are prepared to own a fork. The component is small enough that porting is usually cheaper than building equivalent functionality from scratch, but only if the wrapped JS library is also acceptable. For Livewire 3 projects, a maintained alternative or a short internal build is often the lower-risk choice.