Weave Code
Lang Laravel Package
laravel-lang/lang
Laravel Localizations provides comprehensive language files for Laravel, giving your app ready-made translations for validation, auth, and framework messages across dozens of locales. Install via Composer and ship multilingual apps faster.
Laravel Lang provides ready-to-use localization files for Laravel applications. Install it as a dev dependency and publish the locales you need into lang/ instead of maintaining framework translations manually—covering validation, authentication, passwords, pagination, and more.
- 100+ locales with community-maintained translations
- Includes Laravel’s built-in validation, auth, password, and pagination messages
- Publish files easily via
php artisan lang:addorvendor:publish - Versioned alongside supported Laravel releases
- Install with
composer require --dev laravel-lang/lang
Frequently asked questions about Lang
- What is laravel-lang/lang used for?
- It provides community-maintained translation files for Laravel core messages and several first-party ecosystem packages. You install it via Composer to add or update locale files used by Laravel's trans helper and resources/lang directory. It covers Laravel, Jetstream, Fortify, Breeze, Cashier, Nova, Spark, and Laravel UI translations.
- How do I install laravel-lang/lang in a Laravel application?
- Install the package with Composer using composer require laravel-lang/lang, then publish the language files with php artisan lang:publish. The package does not require service provider or middleware changes. For development-only workflows, some teams install it with --dev and publish translations during setup.
- Which Laravel versions and packages does laravel-lang/lang support?
- It is designed for Laravel applications using the standard localization system, with ecosystem coverage for Jetstream, Fortify, Breeze, Cashier, Nova, Spark, and Laravel UI. The evaluation notes a good fit for Laravel 8+ applications, but you should verify the current Composer constraints against your Laravel version. Always check the package documentation for the latest compatibility details.
- How do I publish translations with php artisan lang:publish?
- After installing laravel-lang/lang, run php artisan lang:publish to copy the package's language files into your application's resources/lang directory. Laravel's normal translation loading and precedence rules then apply. You can publish only what you need or customize the published files afterward.
- Does laravel-lang/lang include translations for Jetstream, Fortify, Breeze, Nova, Cashier, Spark, and Laravel UI?
- Yes. The package provides localization files for Laravel core plus Jetstream, Fortify, Breeze, Cashier, Nova, Spark, and Laravel UI. Coverage is modular, so you can adopt only the languages and framework-specific files relevant to your stack. This reduces manual work for auth-related UI in Jetstream and Fortify projects.
- Can I override laravel-lang/lang translations without editing vendor files?
- Yes. Laravel's translation precedence lets you override package defaults by placing files in resources/lang/{locale}/vendor/lang or the appropriate vendor namespace path. This keeps custom wording intact when the package is updated. You can also publish and edit translations directly if you do not need upstream updates for those files.
- Are all laravel-lang/lang translations complete, especially for passkey and auth error messages?
- Most translations are complete, but the evaluation notes that passkey-related error messages can be missing in some languages, including Bulgarian, Hindi, and Vietnamese. Some validation messages may also have partial coverage, such as a missing encoding rule in Vietnamese. Audit your target locales before relying on them for critical authentication flows.
- Does installing 126+ languages affect Laravel performance or app size?
- Additional language files can increase the amount of translation data shipped with your app, so subsetting to the locales you actually support is a reasonable mitigation. The package uses Laravel's standard .json and .php translation formats, so loading follows normal localization behavior. Test with your own profiling and php artisan optimize:clear if boot time or memory usage is a concern.
- How should I handle missing translations and fall back to English?
- Laravel supports fallback locales via config/app.php and the trans helper, so you can fall back to English when a key is missing. For critical paths, audit target languages for missing keys and add overrides in resources/lang/{locale}/vendor/lang. You can also contribute missing translations upstream to the Laravel Lang repository.
- How do I update laravel-lang/lang translations and test for missing keys in CI?
- Update the Composer package regularly and monitor Laravel core and Jetstream/Fortify releases for new translation keys. Add a CI check or pre-release audit that compares critical translation keys across your supported locales. If you find missing or stale translations, contribute them back to the Laravel-Lang GitHub repository.
Weaver
How can I help you explore Laravel packages today?