- How do I install fabioguin/livewire-searchable-select in a Laravel app?
- Install it as a single Composer dependency with composer require fabioguin/livewire-searchable-select and then use the provided Blade component inside your Livewire form. The package does not indicate any database migrations or backend service changes, so integration is mostly front-end wiring. Confirm the Composer constraints match your Laravel, PHP, Livewire, and Alpine versions before rolling it out, and verify the lockfile and asset build output after upgrading to ^2.0.1.
- Does fabioguin/livewire-searchable-select require Alpine.js?
- Yes. The component pairs Livewire server state with Alpine.js for client-side interaction, including the search term synchronization through $wire.searchTerm. That makes it a strong fit for applications already standardized on Livewire plus Alpine. Teams whose design system prohibits Alpine-dependent components, or whose front end is primarily Inertia, Vue, or React, should look for an alternative.
- Which Laravel, PHP, Livewire, and Alpine versions are supported?
- The available evaluation material does not pin exact supported versions, so treat v2.0.1 as a baseline candidate and check the package's composer.json constraints directly. Verify compatibility against your application's Laravel, PHP, Livewire, and Alpine versions, and confirm how Livewire assets are loaded. Also check whether the package publishes config, views, or JavaScript assets that would require build-pipeline changes.
- How does the search filtering work, client-side or server-side?
- Filtering is driven by Alpine.js client-side interaction while the search term is synced to Livewire via $wire.searchTerm, so the server also sees the current query. Client-side filtering is acceptable for small and medium option lists but becomes the scaling bottleneck for large datasets. For large option sets, plan on server-side search or pagination and load-test the Livewire round trips at your expected option counts.
- How do I bind the searchable select to a Livewire property with wire:model?
- The component manages its own server state through $wire.searchTerm, and you integrate it into the surrounding Livewire form where wire:model handles the selected value. In a sandbox prototype, test search, selection, clicking an already-active option, dropdown close, reset, validation, and nested component updates together. This is important because Livewire morphdom updates are the most likely source of UI state regressions.
- Does it work with Livewire validation and form reset?
- Validation and reset integration are not explicitly documented in the release notes, so validate them yourself before adopting. The critical risk area is UI state synchronization across rerenders, including $wire.searchTerm, selected-state behavior, dropdown lifecycle, and validation or reset flows. Build a sandbox form that exercises validation and reset alongside the component, then pilot in one low-risk form behind a feature flag.
- Is keyboard navigation and screen reader accessibility supported?
- The release notes focus on search-term synchronization, selection click behavior, and dropdown closure, and do not address keyboard navigation or screen reader support. Validate keyboard operation, focus handling, screen reader announcements, and mobile input behavior manually before relying on the component. Run accessibility checks as part of the pilot rather than assuming compliance.
- Will it perform well with large option lists?
- The component's scaling profile depends on how options are sourced, and client-side filtering is only comfortable for small to medium lists. Large datasets likely need server-side search or pagination so you avoid shipping thousands of options to the browser. Load-test Livewire round trips and Alpine reactivity at your expected option counts and form complexity before broader adoption.
- Can I use fabioguin/livewire-searchable-select with Inertia, Vue, or React?
- It is a poor fit for Inertia, Vue, or React front ends because it is built as a Blade and Livewire component with Alpine.js handling the client-side interaction. It is also a weaker choice for heavily customized form systems or teams avoiding Alpine. Adopt it where the stack is already Laravel, Livewire, Alpine, and Blade components.
- Is the package actively maintained and how do I upgrade from an earlier 2.x version?
- For existing users of earlier 2.x releases, upgrade as a patch with composer require fabioguin/livewire-searchable-select:^2.0.1, then verify the lockfile and asset build output. The release notes indicate no breaking changes but do not cover everything, so check the changelog and release cadence and track upstream compatibility with Livewire major versions. Because it is a third-party UI dependency, confirm maintainer responsiveness and whether your team could patch or fork it if needed.