Laravel Translation Scanner Laravel Package

Product Decisions This Supports

• Accelerate i18n/localization rollouts: Eliminates manual translation key extraction, reducing onboarding time for multilingual features by 80%+ for Laravel + Inertia/React projects.
• Build vs. Buy: Justifies buying this package over custom solutions for teams with 5+ languages or Inertia.js/React frontend (where manual extraction is error-prone).
• Roadmap prioritization:
  • MVP for global markets: Ship translatable apps in weeks instead of months.
  • Inertia.js adoption: Critical for React teams migrating to Laravel backend (scans JS/TS/JSX/TSX natively).
  • Developer experience: Reduces context-switching between code and translation files.
• Use cases:
  • Startups scaling internationally (e.g., SaaS with 3+ languages).
  • Legacy Laravel apps needing i18n without refactoring.
  • Design systems with shared strings across PHP/Blade/React.
  • Compliance/localization (e.g., GDPR, regional legal requirements).

When to Consider This Package

Adopt if:

• Your stack includes Laravel 10–13 + Inertia.js/React (or Blade-only with dynamic strings).
• You need automated translation key extraction (no manual copy-pasting).
• Your team supports 3+ languages or plans rapid expansion.
• You prioritize developer velocity over fine-grained translation control (e.g., no need for per-file exclusion rules).

Look elsewhere if:

• You use non-Laravel backends (e.g., Django, Node.js).
• Your app is Blade-only with static strings (consider Laravel’s built-in php artisan lang:publish).
• You need advanced translation context (e.g., pluralization, gender-specific keys) beyond simple string extraction.
• Your team requires custom translation providers (package supports Google/LibreTranslate/Lingva but lacks extensibility hooks).
• You’re on Laravel <10 or >13 (unsupported).
• Security sensitivity: MIT license is permissive, but no audit trail for auto-generated translations.

How to Pitch It (Stakeholders)

Executives (Business/Finance)

*"This package cuts i18n setup time from weeks to minutes for Laravel apps. For example:

• A React + Laravel app with 500 translation strings would take 20+ hours manually—this does it in 5 minutes.
• Cost savings: Eliminates dev time spent chasing missing translation keys (avg. $15–$30/hr).
• Speed to market: Launch multilingual features 3x faster with zero config.
• Scalable: Supports unlimited languages via bulk translation commands. Risk: Minimal—MIT-licensed, zero-config, and non-destructive (only adds missing keys)."*

Engineering (DevOps/DevLeads)

*"Key benefits for the team:

• Zero setup: Install, run php artisan translations:scan, and done. No Webpack/ESLint/config changes.
• Inertia.js first-class support: Scans React/TSX files for t() calls (critical for modern Laravel frontends).
• Local-variable resolution: Handles t(dynamicVar) automatically (no false negatives).
• Provider fallback: Uses Google/LibreTranslate/Lingva with rate-limit protection to avoid API blocks.
• Non-destructive: Safely appends to en.json—no risk of overwriting existing translations. Tradeoffs:
• Limited to string keys (no complex interpolation or pluralization rules).
• Translation quality depends on API providers (but fallback system mitigates this). Recommendation: Pilot on a non-critical feature to validate workflow gains."*

Call to Action: "Let’s test this on [Project X]’s React dashboard. If it saves >5 hours in the first sprint, we’ll roll it out to all i18n projects."