- How do I install akhmads/select-components in a Laravel app?
- Install it with Composer using composer require akhmads/select-components. Laravel package discovery typically registers the service provider automatically, but confirm any manual registration or publish step in the README. Check whether config or view files need to be published before you reference the components in Blade templates. The available evaluation evidence does not confirm the exact setup steps beyond the v1.1.0 release note, so verify against the repository.
- Does akhmads/select-components require npm or a JavaScript build step?
- No. The package is described as Alpine-powered and explicitly designed so you do not need to add a JavaScript build step. You can drop the Blade components into an existing Laravel app without wiring up Vite or npm for them. You will still need Alpine.js available on the page unless the package bundles it, so confirm that detail in the README.
- What Laravel and PHP versions does this package support?
- The only confirmed compatibility signal is release v1.1.0, which added support for Laravel 13. The available evidence does not document a full support matrix, so it is unclear whether Laravel 10, 11, and 12 remain supported or what the minimum PHP version is. Check composer.json on the repository for the authoritative require constraints before adopting it. This is the highest-value thing to verify if you are on an older Laravel major.
- How do I build a searchable select input with these Blade components?
- Use the package's searchable select Blade component in place of a plain HTML select, passing your options as you normally would. The component adds Alpine-powered filtering so users can type to narrow the list. Exact prop names and slot syntax are not captured in the available evidence, so confirm the API in the README or component source. Start with one field in a form and verify the submitted value matches your validation rules.
- Can I create a multiple-select dropdown with akhmads/select-components?
- Yes. Multiple selection is one of the three component types the package advertises, alongside searchable and dependent selects. In a Laravel form you will typically need array-style input names such as options[] so the selected values arrive as an array. Validate that array in your form request and confirm the component renders pre-selected values correctly on edit forms.
- How do dependent or cascading dropdowns work in this package?
- The package ships a dependent dropdown component intended for cases where one select's options depend on another's value, such as country and city. Because the components are Alpine-powered, the dependency handling is client-side rather than a full page reload. The precise data-passing API, such as whether you supply options as JSON or fetch them from an endpoint, is not confirmed in the available evidence. Review the component source before relying on it for large option sets.
- Does it work with Livewire or standard Blade forms?
- The components are Blade components, so they render inside standard Laravel Blade forms and should submit like normal select inputs if the underlying input names are correct. Livewire compatibility is plausible but not confirmed by the available evidence, and Alpine and Livewire can interact in ways that need testing. If you use Livewire, wire up a small prototype and verify model binding, validation errors, and re-rendering behavior before committing.
- Is Laravel 13 supported, and were older Laravel versions dropped in v1.1.0?
- Release v1.1.0 states only that Laravel 13 support was added; it does not say whether Laravel 10, 11, or 12 were removed. A minor version bump that adds a framework major can also raise the minimum PHP or Laravel version, so this needs checking. Inspect the composer.json constraints and the diff between 1.0.x and 1.1.0. If you are on Laravel 11 or 12, pin to 1.0.* in staging until that is confirmed.
- How do I test select components in my Laravel application?
- Test them like any other form input: use Laravel's HTTP tests to submit the form and assert the selected values are validated and persisted correctly. For interactive behavior such as search filtering and dependent option loading, add browser-level tests with Laravel Dusk or a similar tool if those behaviors are critical. The package's own test coverage and CI matrix are not confirmed in the available evidence, so do not assume Alpine behavior is covered upstream. A short smoke test on your key forms is the pragmatic starting point.
- Is akhmads/select-components production-ready, or should I write my own select components?
- Version 1.1.0 indicates a young package, and the available evidence has no signal on maintainer count, release cadence, issue response time, or test coverage. The abstraction risk is also unknown: if the package is a thin convenience wrapper, replacing it with your own Alpine select components may be cheap, which lowers exit cost. For low-risk internal forms it is reasonable to prototype; for critical flows, evaluate the source and pin a version. Laravel packages are generally low-blast-radius dependencies, so removal is usually tractable.