Weave Code
Laravel Translation Faker Laravel Package
fidum/laravel-translation-faker
fidum/laravel-translation-faker generates fake translations for Laravel language files using Faker. Populate missing keys, create realistic demo data, and test multilingual interfaces without writing strings by hand. Ideal for local development and automated tests.
Generates pseudo Laravel language files from another locale to make it easy to see what still needs translating.
Frequently asked questions about Laravel Translation Faker
- What is fidum/laravel-translation-faker used for?
- It generates pseudo Laravel language files from another locale using Faker. It is intended for local development and automated tests where you need realistic translated-looking strings without writing them by hand. It helps exercise __() and @lang calls, populate missing keys, and create demo data for multilingual interfaces.
- How do I install fidum/laravel-translation-faker?
- Install it as a development dependency with composer require --dev fidum/laravel-translation-faker. The package registers its service provider through Laravel package auto-discovery, so no manual provider registration is normally required. Check the README for any optional publishing or configuration steps for your version.
- Which Laravel and PHP versions are supported?
- Version 2.2.0 is described as a compatibility release adding Laravel 13 and PHP 8.5 support. The package targets Laravel 10 through 13 and PHP 8.2 through 8.5, but you should confirm the exact composer.json constraints for your version. Older Laravel majors may need to stay on 2.1.x if the dependency requirements were raised.
- Does fidum/laravel-translation-faker support Laravel 13 and PHP 8.5?
- Yes, version 2.2.0 adds Laravel 13 and PHP 8.5 support according to the release notes. It is a compatibility release with no announced API or behavioral changes. Verify that your orchestra/testbench and illuminate/* constraints resolve cleanly with the new version.
- Should I install fidum/laravel-translation-faker as a dev dependency?
- Yes. It is a test and local-development utility that generates fake translation strings, so it belongs in require-dev. It does not touch the database, queue, cache, HTTP layer, or production container boot path. Keeping it out of production dependencies avoids shipping an unnecessary generator to production.
- How do I generate fake Laravel language files from an existing locale?
- Use the package's generator or facade against an existing locale as the source. It reads that locale's translation keys and uses Faker to produce pseudo translations for the target locale, so your application can render realistic strings. The exact command or API depends on the package version, so follow the README examples for 2.2.0.
- Can fidum/laravel-translation-faker populate missing translation keys?
- Yes, one of its main use cases is filling in missing keys with fake but realistic text. That makes it easier to see what still needs a real translation while keeping the interface functional. It is not a replacement for professional translation; it is a development and testing aid.
- Does it work with Blade templates, __(), and @lang?
- Yes. The generated language files are standard Laravel language files, so they work with the __() helper, @lang directive, and Blade templates that render translations. This lets you test multilingual layouts and localized UI without hand-writing every string. Any Laravel translation loader behavior still applies.
- Can I use fidum/laravel-translation-faker in automated tests?
- Yes, it is designed for local development and automated tests. You can generate fake translations in your test setup so feature and browser tests render localized strings. If your assertions depend on exact output, seed Faker or avoid asserting on generated wording, because fake strings may not be stable across versions.
- Is upgrading from 2.1.x to 2.2.0 safe?
- Version 2.2.0 is a minor compatibility release with no new API, deprecations, or announced behavioral changes, so an in-place upgrade from 2.1.x should be low risk. Update the require-dev constraint to ^2.2, refresh the lockfile, and run tests that assert on rendered translations. Also confirm the composer.json diff did not raise Laravel or PHP minimums that your application does not meet.
Weaver
How can I help you explore Laravel packages today?