Weave Code
Filament Flatpickr Laravel Package
savannabits/filament-flatpickr
Filament Flatpickr swaps Filament's default date picker for the Flatpickr library, adding date ranges, time selection, locales, and flexible formatting to form fields and filters. Simple to install and configure per field.
Flatpickr input for Filamentphp
Frequently asked questions about Filament Flatpickr
- How do I install filament-flatpickr in a Laravel Filament app?
- Run composer require savannabits/filament-flatpickr, then swap the relevant form field to the Flatpickr input class inside your Filament schema. Installation itself is small, but confirm package provenance first, because the Composer name and the linked GitHub repository do not match. The real effort is a few hours for a Filament-fluent developer plus a staging build that proves the assets load on the production asset path.
- Which Filament, Livewire, and PHP versions does filament-flatpickr support?
- Check the Composer constraints in the package's composer.json and confirm your target panel version falls inside that range before adopting it. Filament majors routinely change third-party field APIs and asset registration, so a version that works today may need patching on the next upgrade. Verify the constraints against your own Filament, Livewire, and PHP versions rather than assuming compatibility.
- How do I replace Filament's default DateTimePicker with Flatpickr?
- Replace the DateTimePicker entry in your form schema with the package's Flatpickr field class; nothing else in the schema needs to change. Because it is a presentation-layer adapter, reverting is a one-line swap back to the native picker. Keep adoption to an explicit, enumerated list of fields instead of letting it become the default by accident.
- Does filament-flatpickr support date range selection in a single input?
- Yes, single-input date ranges are one of the main reasons to reach for this package over Filament's native picker. It also supports inline calendars and multi-date selection. Only use it where the native input genuinely falls short, since otherwise you take on dependency risk for no functional gain.
- Can I use Flatpickr for time-only inputs in Filament?
- Yes, time-only inputs and time selection are supported alongside the date modes. That makes it useful for fields like opening hours or appointment slots that the stock picker handles awkwardly. Test the value round-trip through Livewire, including edit-existing-record hydration, before shipping.
- How do I set locales and custom date formats with filament-flatpickr?
- The package exposes Flatpickr locale support and flexible formatting, including friendly altInput-style display formats that differ from the stored value. Configuration is per field, so you can localize one date input without touching the rest of the form. Watch for server versus browser timezone differences when display formats diverge from storage formats.
- Can I disable specific dates in a Filament Flatpickr field?
- Yes, the package supports granular disabled-date rules, which is one of its stronger arguments over the native picker. This suits booking flows, blackout dates, and availability rules. Confirm the disabled logic still behaves after validation-error re-renders, since that is where imperative pickers usually misbehave.
- Do Flatpickr assets load correctly in production with Vite and filament:assets?
- They must register through Filament's real asset pipeline, so a php artisan serve smoke test is not evidence. Run a staging build with the production asset path and confirm the JavaScript and CSS actually load. Treat that staging proof as the minimum bar before go-live is scoped.
- Is savannabits/filament-flatpickr the same package as coolsam/flatpickr on GitHub?
- That mismatch is unresolved and should block installation until someone confirms it in writing. Establish whether these are the same artifact, who holds publish rights, and whether there is a fork chain. Resolving provenance now is cheap; resolving it after the package lands in a release is not.
- Is filament-flatpickr safe and well maintained for production use?
- It has roughly 102 stars, zero dependents, and effectively a bus factor of one, so there is no third-party production validation to borrow confidence from. There is no visible CI or test evidence in the supplied signals, so request it rather than assume it is absent. The bigger production risk is silent data-correctness bugs, such as values stored a day off due to timezone or DST handling, which operators will not report because the screen looks right. Build a QA matrix covering Livewire state sync, validation re-renders, and timezone round-trips as an exit criterion.
Weaver
How can I help you explore Laravel packages today?