- How do I install dashed/livewire-range-slider in a Laravel app?
- Install it with Composer using composer require dashed/livewire-range-slider. Then publish any package assets if the package provides a publish step and include the component in a Blade view. Because the package ships a client-side slider, confirm whether your app needs published JS/CSS or a script tag before rendering it.
- Which Livewire versions does livewire-range-slider support?
- The package is a Livewire component, so it requires Livewire, but the README and repository metadata should be checked for an explicit v2 or v3 constraint. The single March 2024 release predates later Livewire changes, so test wire:model binding on your installed version. Do not assume both Livewire 2 and 3 are supported without verifying composer.json.
- How do I bind min and max values to a Livewire property with a dual-handle slider?
- The component is designed to bind selections to Livewire state with wire:model, but a two-handle control needs a documented convention such as separate minValue and maxValue properties or an array property. Check the package README for the exact property shape before wiring it into validation. Once bound, changes should update the Livewire component without custom JavaScript.
- Does this package require npm or a Vite build step?
- The package advertises zero build step and no npm or bundler requirement, which suggests the slider assets are included or loaded for you. In a real Laravel app, you still need to confirm how the JS and CSS are registered under your asset pipeline, whether Vite, Mix, or CDN. If assets are published, include them once in your layout rather than rebuilding them per form.
- Is dashed/livewire-range-slider safe to use in production?
- It is a small presentation-layer component with no persistence or domain logic, so the technical blast radius is low. The larger risk is sustainability: very low adoption and a single tagged release mean limited field testing and uncertain long-term maintenance. It is reasonable for non-critical UI, but audit accessibility and vendor the code if the control matters to revenue or compliance.
- Does the range slider support keyboard navigation and ARIA accessibility?
- Accessibility depends on the underlying client-side slider widget and how the Livewire wrapper exposes it. The package description does not claim WCAG 2.1 AA conformance, so you must verify keyboard handling, focus states, ARIA roles, and touch behavior yourself. For accessibility-mandated forms, test with a screen reader and consider a maintained native or Filament slider instead.
- How are Livewire updates debounced when dragging the slider?
- The package does not document debounce behavior in the provided overview, and a naive wire:model binding can emit a server round-trip on every handle movement. Use Livewire's deferred or debounced model modifiers, such as wire:model.debounce or wire:model.live.debounce where supported, if you need to limit requests. Test the actual request volume during a drag on your Livewire version.
- Can I customize the slider's min, max, step, tooltips, and number formatting?
- Yes, the package is described as customizable for min/max limits, steps, tooltips, and formatting. Typical usage is to pass those options as component attributes in the Blade tag and then style the slider to match your app. Verify the exact attribute names and supported formatters in the README, since the overview does not list the full API.
- What is the difference between single-handle and dual-handle range sliders in this package?
- Single-handle mode is for choosing one value, while dual-handle mode is for min/max ranges and filtering. The package supports both, so you can use one component for a price filter or a threshold input. For min/max use cases, make sure both handles bind to distinct Livewire properties or a documented array structure.
- Are there alternatives to dashed/livewire-range-slider for Laravel Livewire forms?
- If your app uses Filament, the native Filament slider is the first alternative because it avoids adding an unmaintained dependency. Other options include maintained Livewire slider packages or a small Alpine plus vanilla range input component you control. Compare accessibility, Livewire version support, and asset pipeline fit before choosing a package with a single release.