- What is mrmonat/nova-translatable used for?
- It is a Laravel Nova field that lets you edit spatie/laravel-translatable JSON translation columns per locale directly inside Nova resources. It presents translations as locale tabs and inputs alongside your other resource fields. It is a presentation-layer adapter for admin editing, not a translation storage or routing package.
- Does mrmonat/nova-translatable require spatie/laravel-translatable?
- Yes. The package is explicitly an integration for spatie/laravel-translatable, so the model must already use that package's translatable behavior and JSON-backed translation columns. If spatie/laravel-translatable is not part of your stack, this Nova field has no job to do. It also assumes you are running Laravel Nova, since it is a Nova field.
- How do I install mrmonat/nova-translatable in Laravel Nova?
- Installation is mechanically simple: require the package with Composer, then register the field on the relevant Nova resource. The package does not require schema changes or service-provider surgery according to the assessment. Because the repository is archived, verify the Composer constraints and compiled assets against your Nova version before assuming the install is clean.
- Does mrmonat/nova-translatable support Nova 4 or Nova 5?
- It is not reliably compatible with Nova 4 or Nova 5. The last release was 2021-08-29 and the repository is archived, placing it in the Nova 3.x era. Nova 4 reworked the field lifecycle and moved the asset pipeline from Mix to Vite, and Nova 5 adds further drift, so a 2021-era field plus compiled Vue assets is unlikely to run unmodified on a current Nova major.
- Which Laravel and PHP versions does mrmonat/nova-translatable support?
- The package's Composer constraints reflect its 2021 Nova 3.x-era release, so you should diff its composer.json against your target Laravel, Nova, and PHP matrix. It is not documented as supporting newer Laravel releases or PHP 8.2 and 8.3, and 2021-era PHP code can produce deprecation noise there. Treat the pinned constraints as the first compatibility gate rather than assuming modern support.
- Is mrmonat/nova-translatable still maintained?
- No. The repository is archived, the last release was in August 2021, and it has a single historical maintainer with very low adoption signals. Archived repositories get no CVE triage and no security response process. There is no community to absorb fixes and no downstream canary to learn breakage from, so adopting it means owning it.
- What is the difference between mrmonat/nova-translatable and spatie/nova-translatable?
- spatie/nova-translatable is described in the assessment as the first-party equivalent and is likely the maintained answer. mrmonat/nova-translatable is an archived third-party Nova field for the same spatie/laravel-translatable use case. Evaluating the first-party field costs hours and should happen before forking or adopting this repository.
- Can mrmonat/nova-translatable cause data loss when editing translations?
- Data integrity is the highest-severity risk called out in the assessment. The field's fillUsing and resolveUsing logic is the only guard between an editor and silently clobbering sibling-locale translations, and a stale implementation against a changed Nova field contract is a plausible path to silent content loss. Test saving each locale independently and confirm that other locales remain intact before trusting it in production.
- How do I configure locale tabs and fallback locales in mrmonat/nova-translatable?
- Locale tabs are the core presentation of the field, configured at the Nova resource field level, but the exact archived README options should be verified against your installed version. Custom locale sets and fallback chains are the kind of divergence that could justify a fork rather than reuse. Validate the locale list, fallback display, and save behavior in a staging resource before relying on custom requirements.
- Is mrmonat/nova-translatable safe for production or should I fork it?
- Do not adopt it as a normal transitive dependency. The assessment frames the decision as patch-and-own: the blast radius is limited because Nova is internal back-office tooling, but version skew and potential silent translation loss are real. If Nova 4 or 5 is in use, fork-or-skip is the choice; the field surface is small, plausibly 1-2 engineer-days and around 300 lines, so compare build-with-a-head-start against evaluating the first-party spatie field or building in-house.