Weave Code
Filament Range Field Laravel Package
yepsua/filament-range-field
A Filament form field for range inputs and sliders, letting Laravel admin panels capture single values or min/max ranges with a simple, native-feeling component that integrates directly into Filament forms.
yepsua/filament-range-field adds a range slider field to Filament forms, letting users pick a minimum and maximum value with a single dual-handle control. It's a natural fit for filtering by price, dates, or any numeric interval in admin panels and dashboards.
Built on noUiSlider, the field integrates cleanly with Filament's form schema and state handling.
- Dual-handle range selection with configurable min, max, and step
- Filament-native field API for quick form integration
- Customizable slider behavior and formatting
- Returns values as a simple array pair (
[min, max])
Frequently asked questions about Filament Range Field
- What Filament and Livewire versions does yepsua/filament-range-field support?
- The package is built as a Filament 3 form field and targets Laravel 10 or 11, PHP 8.1+, Livewire 3 and Filament 3.x. Its last release was December 2023, which predates Filament 4, so it will almost certainly fail to install alongside a v4 panel. Read the composer.json constraints rather than the README before committing, and confirm the resolved versions against your actual composer.lock.
- How do I install and use the range field in a Laravel Filament panel?
- Install it with composer require yepsua/filament-range-field, optionally publish the views, then add RangeField::make('weight') to your form schema. Because the package is effectively unmaintained, pin an exact tag instead of a floating constraint and record the resolved version in your dependency decision log. Budget a half-day spike for an engineer already familiar with custom Filament fields.
- Does this package support a two-handle (dual thumb) range slider?
- The package advertises both single and dual handle modes, so a two-thumb range is intended to be supported. Most packages marketed as range fields only offer a single thumb, so verify the dual-handle API on the exact tag you install and confirm both values bind correctly to your Livewire model property. Test the dehydrated state carefully, since a dual value is usually an array rather than a scalar.
- How do I configure the minimum, maximum and step values on the range field?
- Min, max and step are configurable on the field itself, typically through chainable methods alongside the standard Filament field API. Check the defaults after installation, because an unset step can produce fractional values you did not expect. Whatever you configure in the browser must also be mirrored in your Laravel validation rules.
- Is the range slider value validated on the server, or only in the browser?
- Only the browser restricts the handle position, and that is not server-side enforcement. You must add explicit Laravel validation rules for min, max, step or between, otherwise a crafted request can submit out-of-range values and the field becomes a validation bypass. Treat the slider purely as a UI affordance and always validate the numeric payload on the backend.
- What data type does the Filament range field store, string or integer?
- HTML range inputs return strings from the DOM, so the value may arrive as a string unless the field casts it. Verify integer and float casting, nullable handling, and whether Livewire state dehydration runs as expected before relying on it. Round-tripping into an integer database column is the most likely place to see silent type coercion and bad data.
- Is yepsua/filament-range-field still actively maintained?
- It is effectively a hobby package: a single maintainer, no release in roughly two years, about 36 stars and zero dependents. There is no evidence of a test suite or CI running against current Filament releases. Treat it as unmaintained source you are prepared to adopt and fork, not a supported dependency you can raise issues against.
- What happens to this package when I upgrade to Filament 4?
- The last release predates Filament 4, so the package most likely constrains to ^3.0 and will not install cleanly on a v4 panel. Filament's form component API is internal and has historically broken across majors, so working on v3 does not imply forward compatibility. If a v4 upgrade is on your roadmap, do not adopt the package; vendor the source or rebuild the field internally instead.
- Can I build the range field myself instead of depending on this package?
- Yes, and for many teams that is the safer route. The implementation is a small Blade partial plus a Field subclass registered through the panel, which is roughly one to two developer days including tests. Vendoring the source into app/Filament/Forms/Components under your own namespace removes the abandonment risk and makes the Filament 4 delta something you control.
- Does the range field handle accessibility, dark mode and RTL layouts?
- Keyboard support, ARIA labelling, dark mode and RTL behaviour are undocumented, so treat accessibility and theming as low-to-medium risk until you check them yourself. Also confirm the component's assets are registered through FilamentAsset, because a missing registration shows up as an unstyled native slider rather than a visible error. If you are outside Filament entirely, use a native numeric input instead of pulling in the framework scaffolding.
Weaver
How can I help you explore Laravel packages today?