- What is rvxlab/filament-colorpicker used for?
- It is a Filament form-field plugin that registers a color picker component for Filament forms. Users can choose colors visually, preview the selection, and store the value with minimal setup. It is typically used in admin panels and resource forms that need a color input.
- How do I install rvxlab/filament-colorpicker?
- Install it with Composer using composer require rvxlab/filament-colorpicker. Laravel package discovery registers the service provider, so no manual provider entry is normally required. Then add the package's field class to your Filament form schema.
- Which Laravel and Filament versions does filament-colorpicker support?
- The package targets Laravel applications running Filament 2.x. Its deprecation notice is aligned with the Filament 2.x documentation, so its useful life is bounded by your Filament 2.x lifetime. Filament 3 ships its own ColorPicker with a different API surface, so check Composer constraints before upgrading.
- Is rvxlab/filament-colorpicker still maintained?
- No. Release 1.4.2 is a documentation-only deprecation notice with no code changes. There will be no further bug fixes, compatibility patches for future Laravel or Filament majors, or security response path. Treat it as an abandoned dependency and schedule removal.
- How do I replace filament-colorpicker with Filament's built-in ColorPicker?
- Inventory every reference to the package's field class, then swap imports to Filament\Forms\Components\ColorPicker. Verify method parity for the options you actually use, such as format, alpha toggles, and default values. Run form-level tests or manual QA on each affected screen, then run composer remove rvxlab/filament-colorpicker and delete any published config or assets.
- What format does filament-colorpicker store values in?
- It typically stores colors as a hex string, with alpha handling depending on the options you enable. Before migrating, confirm what format your database actually holds and whether Filament's built-in field emits the same value. Stored-data assumptions are the real migration risk, not the field class itself.
- Does Filament have a built-in color picker field?
- Yes. Filament provides Filament\Forms\Components\ColorPicker in the same namespace family as other form components. It composes with existing form schemas, validation, and reactive fields without adaptation. That first-party field is the recommended replacement for this package.
- Can I use filament-colorpicker in production?
- It still works on a pinned version, but it is unmaintained and has no upstream support. Any defect after 1.4.2 is yours to fork or work around, and future Filament or Laravel majors may break it at class-load or form-render time. Short-term use is acceptable only if removal is explicitly scheduled.
- How do I test forms that use filament-colorpicker?
- Use Filament and Livewire form testing helpers to set the field state and assert the submitted value, covering the format and alpha behavior you rely on. Run those tests before and after swapping to the built-in ColorPicker to confirm identical output. Manual QA on each affected screen is also recommended for reactive or dependent fields.
- What happens if I upgrade to Filament 3 while filament-colorpicker is installed?
- It will likely break at class-load or form-render time because Filament 3's built-in picker has a different API surface. Sequence the removal before or alongside the Filament upgrade rather than after it, so you are not debugging two variables at once. If you are already mid-upgrade to Filament 3, fold this removal into that work item.