Weave Code
Nova Translation Laravel Package
armincms/nova-translation
A Laravel Nova tool for managing application translations from the Nova dashboard. Browse and edit translation keys and language files through a convenient interface, simplifying multilingual app maintenance without manual file edits.
Nova implementation of the armincms/database-localization.
Frequently asked questions about Nova Translation
- What is armincms/nova-translation and what does it do?
- It is a Laravel Nova tool that provides a dashboard interface for managing application translations. Instead of editing PHP or JSON language files by hand, you browse and edit translation keys for each locale inside Nova. It is built as the Nova implementation of the armincms/database-localization package, so the underlying localization storage and lookup come from that library.
- How do I install armincms/nova-translation with Composer?
- Install it with composer require armincms/nova-translation, which uses standard Laravel package auto-discovery to register the service provider. After installing, publish the package config and any shipped assets with php artisan vendor:publish, then register the tool in your NovaServiceProvider. Because it is a Nova tool, Nova must already be installed and licensed in the same application.
- Does this package work with Laravel Nova 3?
- No. Version 2.0.0 of the package is a major release whose stated change is the upgrade to Nova 4, so its Composer constraint will not coexist with Nova 3. If you are still running Nova 3, stay pinned to the package's v1.x line until you schedule the Nova major upgrade. Treat the Nova 3 to Nova 4 move and this package bump as a single, planned change.
- What Laravel and PHP versions does nova-translation require?
- The package targets the Nova 4 baseline, which requires Laravel 9 or newer and PHP 8.1 or newer. Nova 4 also replaced the Nova 3 front-end build with Vite, so any shipped compiled assets need to be compatible with that toolchain. Check your pinned Laravel and PHP versions before adopting, since Nova's floor may exceed your current runtime.
- Is there an upgrade guide from v1 to v2 of this package?
- The v2.0.0 release note is a single line stating the Nova 4 upgrade, and no migration guide or changelog detail was provided with it. That means you cannot confirm from the release notes whether config keys, public APIs, published asset paths, or Vue component contracts changed. Before upgrading, diff the published config and tool registration against your current setup and test the admin UI manually.
- How is nova-translation related to armincms/database-localization?
- Nova-translation is the Nova presentation layer for the armincms/database-localization package, which handles the actual localization storage and resolution. Installing the tool implies adopting that underlying library and its translation loading behaviour. If you already use database-backed translations, this package gives you a UI over that data rather than a parallel system.
- Can I use nova-translation without Laravel Nova?
- No, it is not a general-purpose Laravel localization library. The package plugs into Nova's tool and field surface, and Nova is a commercial, license-gated first-party package. If your application does not use Nova, there is no integration path and you should look at a standalone translation manager instead.
- Does it edit language files on disk or store translations in the database?
- The tool sits on top of the database-localization layer, so translation values are managed through that package's storage mechanism rather than through manual file edits. The Nova UI is a convenience for browsing and editing keys per locale without opening files. Verify against your own published config how the underlying package resolves and caches those values at runtime.
- What are the production risks of upgrading to nova-translation v2?
- The upgrade is breaking by definition because it follows a Nova major version and drops Nova 3 support, so Nova and this package must move in lockstep. Nova 4's front-end toolchain changes can break custom tools and fields in ways that only appear at runtime in the admin UI, not in PHP test suites. Pin exact versions in composer.json, commit the resolved lockfile, and run composer why-not laravel/nova 4.* on a scratch branch to surface conflicts early.
- Who maintains nova-translation and how actively is it developed?
- The package is published by armincms and its release cadence is tied to Nova major versions, with v2.0.0 focused solely on Nova 4 support. No repository metadata on maintainer count, commit recency, test coverage, or CI status was provided, so assess the GitHub repository directly before committing. Because risk inherits from Nova's own licensing and release cadence, plan for the possibility of slow turnarounds on future Nova upgrades.
Weaver
How can I help you explore Laravel packages today?