Weave Code
Laravel Find Missing Translations Laravel Package
diglabby/laravel-find-missing-translations
A Laravel artisan command that scans your app for translation keys and reports any missing from your language files, so you can keep every locale complete and catch untranslated strings before they ship.
Artisan command to find missing translations
Frequently asked questions about Laravel Find Missing Translations
- What is diglabby/laravel-find-missing-translations used for?
- It is a Laravel Artisan command that scans your application for translation keys and reports any keys missing from your language files. It helps teams keep every locale complete and catch untranslated strings before they ship. It is best treated as development-time quality tooling rather than a production runtime dependency.
- How do I install laravel-find-missing-translations in a Laravel app?
- Install it as a Composer dev dependency in your Laravel project and invoke it through the Artisan console workflow. It should not require schema changes, runtime services, or production configuration. Pin the version initially, for example to ^1.8.1, and review upstream releases before widening the constraint.
- Which Laravel and PHP versions does laravel-find-missing-translations support?
- You should confirm the supported Laravel and PHP ranges from the package Composer constraints and README before standardizing on it. The 1.8.1 release is described as a patch-level maintenance release with no indicated breaking changes. Verify it against your team's Laravel and PHP matrix, especially if you use JSON or namespaced translations.
- How does the command find missing translations?
- It scans your application code for translation keys and compares them against the entries present in your language files. Because this is static detection, dynamically constructed keys and variable-based locale selection can produce false positives or false negatives. Validate the output against a representative baseline before making the check blocking.
- Can I run laravel-find-missing-translations in CI as a blocking check?
- Yes, it fits naturally into local checks and CI, but start in warning-only mode to understand false-positive rates. First capture a baseline, classify findings as true missing translations versus static-analysis limitations, and agree on exclusions. Then promote it to a blocking pull-request check once the command's exit-code behavior is confirmed for your setup.
- Does it support JSON translation files, nested PHP arrays, and namespaced or vendor translations?
- Its strongest fit is Laravel applications that rely on standard lang and translation file conventions. Support for JSON translations, nested PHP files, namespaced package translations, and vendor translations should be verified against your actual file layouts. Test a representative project before relying on the command for full locale coverage.
- Why does laravel-find-missing-translations report false positives for dynamic translation keys?
- Static translation-key detection cannot always resolve keys built from variables, concatenation, or runtime locale selection. Vendor and package translations or non-standard file layouts can also lead to inaccurate results. Use a baseline and exclusion rules for intentionally dynamic keys, and recheck findings as the codebase evolves.
- How do I exclude generated code, third-party paths, or known keys from the scan?
- Identify the package's configuration points for excluding paths and intentionally dynamic keys, and confirm them in the README before enforcing the check. Establish exclusion rules after reviewing a baseline run so you do not hide real missing translations. Keep the exclusion list curated as your application and dependencies change.
- What changed in laravel-find-missing-translations 1.8.1?
- Version 1.8.1 fixes locale detection so a locale is recognized in either supported format. It also improves verbose output by naming the relevant file, which makes results easier to diagnose. The release is a targeted bug fix with no indicated breaking changes, deprecations, or new feature surface.
- What alternatives exist to laravel-find-missing-translations?
- Alternatives include manual translation audits, custom scripts, or other static-analysis tooling that checks translation usage. This package is narrowly scoped as a Laravel Artisan development tool, so its value depends on your existing lang conventions and CI workflow. Compare it by running a proof of concept against your current branch and measuring false positives before adopting it.
Weaver
How can I help you explore Laravel packages today?