Weave Code
Nova Color Field Laravel Package
optimistdigital/nova-color-field
A Laravel Nova color picker field that adds an easy-to-use color input to your resources, letting you choose, preview, and save colors in Nova forms with simple configuration.
A Laravel Nova Color Picker field.
Frequently asked questions about Nova Color Field
- How do I install the Laravel Nova color picker field?
- Install it with Composer using the package name shown on Packagist, then add a use statement for the field class and one ColorField entry inside your resource's fields() method. No config publishing or consumer-side build step is required if compiled assets are included in the distribution. Because the project moved from optimistdigital to outl1ne, confirm the current Composer name before requiring it.
- Which Laravel Nova versions does nova-color-field support?
- The assessment says the only reliable answer is the declared Nova constraint in the package's composer.json, so inspect that directly rather than inferring support from a release date. Nova major versions are the highest compatibility risk for third-party fields because the field-asset contract and Vue version changed at Nova 4 (Vue 2 to Vue 3). Nova 5 support should be treated as unconfirmed until the constraint and changelog show it.
- Does this package work without Laravel Nova?
- No. This is a Laravel Nova field only: a PHP Field subclass plus a compiled Vue component that renders inside Nova create, edit, index, and detail views. It is not a Blade component, not an Inertia or Vite asset, and cannot be reused outside Nova. Using it therefore inherits Nova's paid licensing terms, upgrade cadence, and vendor risk.
- What database column should I use for a Nova color field?
- Use varchar(7) for a standard #RRGGBB hex value, or varchar(9) if alpha is permitted and you store #RRGGBBAA. Lock that decision before the migration ships, because a 7-character column paired with an alpha-capable picker is a truncation bug waiting to happen. Truncation issues are typically surfaced by users rather than tests.
- Does nova-color-field support alpha or opacity in colors?
- Alpha support is one of the open questions the assessment flags, so verify it in the package docs and field options before designing your schema. If the picker can produce an alpha channel, the storage column must be varchar(9); if it only produces #RRGGBB, varchar(7) is sufficient. A mismatch between picker capability and column length causes silent truncation.
- Is optimistdigital/nova-color-field still maintained after the outl1ne rename?
- The repository has moved from the optimistdigital namespace to outl1ne, so confirm whether the old Packagist name is abandoned with a replacement or still shipping. Also check whether the PHP namespace changed, because installing both packages can produce two copies installed and class-not-found errors. The assessment also warns that the recorded last release date looked forward-dated and should be verified against the real tag list and commit history.
- How do I show a color swatch in Nova index and detail views?
- The field renders a color picker in create and edit forms and a swatch in index and detail views, so you normally just add the field to your resource's fields() method. The assessment describes it as presentation-layer only, with no middleware, queues, scheduled work, or external services. Check the README for any field-specific options such as preview or swatch configuration.
- Does the package ship compiled assets or require an npm build?
- No consumer-side Node build is required if the compiled Vue assets are shipped in the distribution, and the assessment notes no config publishing is needed. However, the assessment explicitly asks reviewers to confirm whether compiled assets are included rather than assuming. Verify the dist contents and the install instructions before rollout.
- How do I validate hex colors saved by the Nova color picker?
- The assessment warns that if the field accepts free-text hex without server-side validation or normalization, invalid or over-length values can land silently in the database. Pair the field with a Laravel validation rule for hex format and length, and enforce the column size at the database layer. Client-only validation is not enough for production data integrity.
- How does nova-color-field compare to building a native color input myself?
- The package is a low-effort, additive dependency: Composer require, one use statement, and one field line, with realistic delivery under a day including QA. The build alternative is roughly a ten-line native color input plus a hex validation rule, about half a day, but that becomes a perpetual ownership cost. The main risks are Nova major-version coupling, a single maintainer, the namespace migration, and unverified release metadata, so treat it as yes if the compatibility gates clear.
Weaver
How can I help you explore Laravel packages today?