Weave Code
Laravel Nova Lang Laravel Package
coderello/laravel-nova-lang
A Laravel Nova tool for managing app translations directly from the admin panel. Browse and edit language files, add locales, and keep multilingual content organized without editing files manually.
Language support for Laravel Nova.
Frequently asked questions about Laravel Nova Lang
- How do I install coderello/laravel-nova-lang in a Laravel Nova project?
- Install it with Composer, typically as a dev dependency since it ships translation files rather than runtime code, then publish the assets with php artisan vendor:publish and select the package's provider tag. There is no service provider logic, migration, or middleware to register in your application. Because it is data-only, you can also just copy the lang files into your project and drop the dependency entirely.
- Where do the Nova translation files get published to?
- They land in the Nova vendor translation path, lang/vendor/nova/{locale}. On Laravel 9 and later the default lang directory moved from resources/lang to the project root lang/, so confirm which path your application actually loads. Add the publish step to your deployment pipeline or CI, otherwise the files drift between environments.
- Does this package translate my application strings or only the Nova admin panel?
- It localises strings only for the Laravel Nova interface, not your own application's content or validation messages. It does not deliver RTL layout, since Nova has no first-class RTL support, and it does not add localised date or number formatting beyond what Carbon and your app locale already provide. Treat it as a localisation asset for the Nova admin UI, separate from your application's own translation workflow.
- Which Nova and Laravel versions does coderello/laravel-nova-lang support?
- The translation keys are version-locked to Nova's internal translation namespace, which the package does not control. Release 2.0.2 refreshed the English baseline from a recent Nova version, but confirm which Nova major that baseline targets before relying on it for a Nova 5 install. If the key sets diverge, missing keys silently fall through to English or render raw dotted keys in the target locale.
- How do I add a new locale for the Nova admin panel?
- Publish the package assets and add a directory under lang/vendor/nova/ named with the locale code, for example lang/vendor/nova/pt_BR. Copy the English files as a starting point and translate the values while leaving the keys untouched. Only a subset of the bundled locales is actively refreshed, so verify key parity against the current English baseline. After the first locale, each additional locale costs very little setup effort.
- Why do missing translations show English or raw dotted keys in my locale?
- Nova falls back to your fallback_locale when a key is absent, and you may still see a raw dotted key if neither the locale file nor the fallback defines it. Set config/app.php fallback_locale to en so degradation is predictable. Missing keys are only visible in the target locale, so English-language QA will not catch them, which makes a key-diff check against the English baseline mandatory after every Nova upgrade.
- Is coderello/laravel-nova-lang safe to use in production?
- It is MIT-licensed and data-only, with no service provider logic, middleware, database surface, or API contract your application code can couple to, so runtime risk is near zero. The real risk is version drift, because the keys track Nova's internal namespace and a Nova upgrade can invalidate the refreshed locales. Pin the version, add a key-diff gate to your upgrade runbook, and keep fallback_locale set to English so degradation is predictable.
- What is the maintenance status of coderello/laravel-nova-lang?
- Release 2.0.2 is evidence the project is maintained rather than abandoned, which is a real improvement over the previous 2023 release. It is not evidence of a formal support commitment: the maintainer footprint is small and there are effectively zero declared Composer dependents, since most consumers copy files rather than install it. Keep your own published copy or fork in mind as a fallback.
- Which locales are up to date in this Nova language package?
- Release 2.0.2 refreshed German, French, Spanish, Russian, Dutch, and both Chinese locales, and added Latvian. The remaining long tail is now further behind the refreshed English baseline, so coverage is bimodal. Prioritise the refreshed set for production locales and review any other locale before shipping it.
- How do I verify translations after upgrading Laravel Nova?
- Republish the files, then diff the English key set against the Nova version you actually run to find keys that were added, renamed, or removed. Load the Nova panel in each production locale instead of relying on English-language QA. If the installed package exposes a command for pulling or diffing Nova's own language files, confirm whether it ships in production autoload or is dev-only before adding it to your upgrade runbook.
Weaver
How can I help you explore Laravel packages today?