Weave Code
Nova Locale Field Laravel Package
optimistdigital/nova-locale-field
A Laravel Nova field for multilingual admin interfaces. Add locale selection to Nova forms and manage localized resource values with a simple, configurable field from Optimist Digital.
A Laravel Nova field.
Frequently asked questions about Nova Locale Field
- What does optimistdigital/nova-locale-field do?
- It is a Laravel Nova form field that adds locale selection to Nova resource forms so editors can manage localized values per locale. It is scoped entirely to the admin surface and does not handle runtime locale negotiation, routing, or query scoping. Think of it as a backoffice content-editing helper, not an i18n framework.
- How do I install nova-locale-field in Laravel Nova?
- Install it with Composer using composer require optimistdigital/nova-locale-field, then register the field in the fields method of your Nova resource and configure the locale list. Mechanically it is trivial and a Laravel developer can have it rendering in under an hour. The real blocker is version alignment with your Nova major version, not installation effort.
- Does nova-locale-field support Nova 4 or Nova 5?
- Assume it does not until you prove otherwise in a spike. The last release was February 2021 and targets the Nova 3 era with Vue 2 field components, while Nova 4 moved to Vue 3 and Nova 5 followed. A field of that vintage should be treated as non-functional on Nova 4 or 5 without a port.
- Is optimistdigital/nova-locale-field still maintained?
- No. The repository is archived, the last release was in February 2021, and it has around 17 stars with no active community. There are no security patches, no PHP 8.2+ or Laravel 10/11 compatibility work, and no Nova 4/5 support. Adopting it means you inherit the maintenance obligation immediately.
- What Laravel and PHP versions does nova-locale-field support?
- The package targets the Nova 3 era, which implies PHP 7.x through 8.0-era constraints and older Laravel versions from that period. It has not received compatibility updates for PHP 8.2+ or Laravel 10 and 11. Verify constraints in the composer.json before assuming it will install cleanly on a modern stack.
- How do I configure the locale list in nova-locale-field?
- You configure the available locales when registering the field in your Nova resource, typically as an array of locale codes the field should offer. The field is described as simple and configurable, so the main setup is the locale list plus the underlying persistence shape. Confirm that the field writes the same data shape your API and frontend read before relying on it.
- Does nova-locale-field work with spatie/laravel-translatable?
- It can fit a JSON-column translation model such as spatie/laravel-translatable, but the package does not enforce a persistence model by itself. Its value depends entirely on whether your localization is JSON-column translation, per-locale child rows, or locale-scoped field groups. Confirm that assumption first, because the wrong model invalidates the whole evaluation.
- What are alternatives to nova-locale-field for multilingual Nova forms?
- Consider spatie/nova-translatable, a first-party Nova 4/5 field, or a hand-rolled locale tab component in your own codebase. Because the field only touches the admin form, replacement is usually a UI swap plus a data-shape verification rather than a deep migration. A maintained alternative is typically cheaper than porting an archived field.
- Can I fork or vendor nova-locale-field for production use?
- Yes, but treat it as a fork candidate rather than a dependency you adopt on faith. Vendor or fork it so you control patches, and assign an explicit owner plus a trigger date to retire the fork. Given the small surface area, porting the field component to the current Nova field API is feasible if the UX is load-bearing for editors.
- What are the risks of using an archived Nova field in production?
- The main risks are abandonment, version drift, and silent data corruption such as partial locale saves or fallback overwrites. Security surface is low because it is a form field, not an auth, upload, or query-layer component. The package also depends on Nova, a paid closed-source admin panel, so your ability to patch it is bounded by Nova's own extension API stability.
Weaver
How can I help you explore Laravel packages today?