- How do I install teofanis/searchable-dropdown in a Laravel app?
- Install it with Composer as a normal Laravel package, then publish any required frontend assets and reference the component in your Blade form. Because 2.0.1 adds Livewire v3 support, confirm your app is on a compatible Livewire version before adopting 2.x. Follow the repository README for exact service provider, asset, and component usage details.
- Does searchable-dropdown 2.x support Livewire v3?
- Yes, the 2.0.1 release adds Livewire v3 support via PR #13, making 2.x the line to evaluate for Livewire v3 applications. The release note is sparse, so confirm Laravel, PHP, and Livewire constraints in the package metadata and test in staging. If you are still on Livewire v2, do not assume 2.x is compatible without explicit confirmation.
- Is teofanis/searchable-dropdown compatible with Livewire v2?
- The available release note only confirms Livewire v3 support and does not state whether 2.x remains dual-compatible with Livewire v2. Treat 2.0.1 as potentially breaking for Livewire v2 estates and pin to the 1.5.x line if the feature is already working there. Verify with a branch and browser smoke tests before changing Composer constraints.
- What Laravel and PHP versions does searchable-dropdown 2.0.1 support?
- The 2.0.1 release note does not document the supported Laravel, PHP, or Livewire version matrix, so compatibility must be confirmed from composer.json, the README, or the maintainer. Record the versions you actually test in an internal compatibility note. Do not assume the major version bump preserves the same platform constraints as 1.5.2.
- What breaking changes are in searchable-dropdown 2.0.1 from 1.5.2?
- The jump from 1.5.2 to 2.0.1 is a major-version change, so treat it as potentially breaking until proven otherwise. Check for changes to component names, props, events, views, config keys, and published assets. Ask the maintainer for a migration guide or run a focused spike before upgrading production forms.
- How do I migrate from searchable-dropdown 1.5.2 to 2.0.1?
- Use a conservative migration: inventory Livewire and Laravel versions, identify every screen using the package, create a branch, update Composer constraints, re-publish assets if required, clear compiled views and caches, then run application tests and browser smoke tests on dropdown-heavy forms. If you are also moving from Livewire v2 to v3, complete and stabilize that upgrade first, then introduce searchable-dropdown 2.x. Keep a pinned rollback to the prior package version.
- Can searchable-dropdown handle remote search and pagination for large option sets?
- If the dropdown performs remote search through Livewire, expect additional requests per user interaction and review debounce, pagination, and result caching. If filtering is local to the option list, scaling risk is much lower. Also validate keyboard behavior, accessibility, and event handling after Livewire upgrades.
- How should I test searchable-dropdown in a Laravel application before production?
- Run a staging pilot and smoke-test every dropdown-heavy form, including component aliases, Blade directives, event names, asset paths, and config keys. Clear compiled views and caches, verify the Livewire request lifecycle, and include the supported PHP, Laravel, and Livewire versions in CI coverage. Have a rollback plan to the previous package version before production rollout.
- Is teofanis/searchable-dropdown suitable for admin panels and form-heavy Laravel apps?
- It is a reasonable fit for admin panels, internal tools, and form-heavy Laravel applications already standardized on Livewire v3. The package sits in the Blade/UI layer with low coupling to domain logic, so keep it isolated to presentation-layer usage. Mixed estates need more validation, and Livewire v2 applications should pin 1.5.x unless compatibility is confirmed.
- What alternatives exist for Laravel searchable select components?
- Alternatives include building a focused Livewire searchable select, using a JavaScript select library, or keeping native selects for short lists. Compare accessibility, remote search behavior, asset footprint, and upgrade maintenance before choosing. For this package, pin the Composer constraint and test the Livewire upgrade path in staging.