- How do I install daguilarm/livewire-combobox in a Laravel app?
- Install it with composer require daguilarm/livewire-combobox, then publish any package views or configuration if the README instructs you to. Register or include the Livewire component in a Blade view and pass the model and column mappings it needs. Because the package is archived and Livewire 2-era, confirm its composer.json constraints before installing in a current Laravel app.
- Which Laravel and Livewire versions does livewire-combobox support?
- The last release was 2021-05-12, so the package is built for the Livewire 2 era rather than Livewire 3 or 4. Check its composer.json for pinned livewire/livewire and laravel/framework constraints before assuming compatibility. If it pins Livewire ^2.0, adopting it forces a framework-wide version freeze.
- How do I create dependent selects with multiple levels in Livewire?
- The component renders a cascade of dependent select inputs and repopulates child options from Eloquent when a parent value changes. You configure model and column mappings, and recursive Blade rendering supports arbitrary nesting depth. Each change is a Livewire server round-trip, so scope queries and limit option counts.
- Does livewire-combobox work with Livewire 3?
- Probably not without changes: Livewire 3 made wire:model deferred by default, renamed lifecycle hooks, replaced $emit with dispatch, and requires a single root element in views. The package's Blade templates and event wiring are likely to violate those rules. Treat any composer require success as misleading and plan a fork or rewrite.
- Is livewire-combobox safe for production?
- The upstream repository is archived, so there are no bug fixes, security patches, or CVE response. It also has low adoption, a single maintainer, and no visible CI or test suite. For production, fork and vendor the code under MIT or reimplement the dependent-select pattern natively.
- How does livewire-combobox perform with large option lists?
- Every select change triggers a server round-trip, which is acceptable for admin filters or back-office screens but poor for anonymous high-traffic public forms. Large option lists increase query volume and payload size per interaction. Add limits, indexes, and per-tenant scoping if you keep the component.
- Can livewire-combobox be used for searchable autocomplete or combobox inputs?
- The package is described as a searchable Livewire combobox with server-side searching and dynamic options, so it can serve autocomplete-style form inputs without custom JavaScript. Its stronger differentiator is the recursive dependent-select cascade with configurable model mappings. Verify the actual view behavior in the repo before relying on search features.
- What are alternatives to livewire-combobox for dependent dropdowns in Laravel?
- For Livewire 3, a native dependent-select component is roughly 100–200 lines: an array of selected values, a recursive Blade partial, and an updated hook that clears descendants. You can also use actively maintained UI kits such as WireUI or Filament forms for searchable selects. Alpine.js can handle lightweight client-side filtering when the option set is small.
- How should I secure dropdown option queries in livewire-combobox?
- Option queries are driven by user input, so an unscoped dropdown can become a record enumeration endpoint. Route option queries through your policy or authorization layer and scope them per tenant or user. The archived package will not receive fixes, so audit and harden any fork you deploy.
- How do I test a Livewire combobox component?
- The package itself shows no evidence of a test suite, so do not rely on its tests for confidence. In your app, use Livewire::test to set a parent value, assert the child options, and verify descendant values clear correctly. Add authorization tests proving users cannot enumerate records outside their tenant.