- What does norman-huth/nova-values-field do?
- It adds a flexible values field to Laravel Nova for editing repeatable lists or key-value-style data in the admin UI. The field persists a flat array of values as structured JSON on an Eloquent model, making it useful for settings, metadata, tags, and custom attributes. Architecturally it is a thin Nova form field with no service layer, migrations, or domain logic.
- Is norman-huth/nova-values-field still maintained?
- No. The repository is archived and the package is explicitly marked as no longer maintained, with the README pointing to maintained alternatives. That means there are no upstream fixes for Nova or Laravel upgrades, and the Composer name norman-huth/nova-values-field does not match the Muetze42 hosting org, so provenance should be verified before use.
- How do I install norman-huth/nova-values-field?
- Install with composer require norman-huth/nova-values-field and register the field in a Nova resource. You need Laravel, an active Nova license, PHP 8.x, and a JSON-castable column on the target model. Because the repository is archived, pin a commit or vendor the source rather than relying on upstream updates.
- Which Laravel and Nova versions does nova-values-field support?
- The package does not publish a confirmed support matrix in the provided material, so inspect composer.json for constraints on laravel/nova and illuminate/* before assuming compatibility. The repository was archived around mid-2025, so assume nothing beyond the Nova generation current at that time. Nova field APIs and asset pipelines change between majors, so test against your exact Nova version.
- What are maintained alternatives to nova-values-field?
- The README points to maintained alternatives, and Nova's built-in KeyValue field covers similar keyed data. Because this field is a very thin wrapper of roughly 50 to 100 lines, scaffolding a first-party field with php artisan nova:field is often the cheapest maintained option. Forking is another route, but you then own the Nova compatibility work.
- How does nova-values-field store data, and which database column do I need?
- It stores a flat array of values as structured JSON in a JSON or text column on the Eloquent model. The model must be able to cast that column to an array, and no migrations are shipped with the package. Confirm the exact stored shape in a spike before relying on it.
- How is nova-values-field different from Nova's KeyValue field?
- The package describes itself as a clone of the KeyValue field without keys. KeyValue stores keyed entries, while this field persists a flat list of values. If you switch between them, existing records need a one-time data migration or an accessor and mutator to normalize reads during transition.
- Can I use nova-values-field in production?
- Treat it as high risk. It is archived, single-maintainer, has near-zero adoption at 6 stars and 0 dependents, and no visible test suite, so there is little evidence of production use. If you must use it, fork it into nova-components or a private namespace, pin the commit, add tests, and document an upgrade runbook.
- How do I migrate existing KeyValue data to nova-values-field?
- Map each keyed KeyValue record to the flat array shape the values field expects, either in a one-time migration or through model accessors and mutators during transition. Include a rollback path and verify render, save, retrieve, validation, and reorder flows against your Nova version. Test on a branch before touching production data.
- Does nova-values-field have tests, and can I rebuild its JS assets?
- There is no visible test suite and the JS asset build reproducibility is unclear from the material provided. Run the field through render, save, retrieve, validation, and reorder in a spike, and confirm the frontend build works on your Nova version. If you vendor it, add a minimaltest suite and CI for the JS build.