i18n Key Generator for Large-Scale Projects

i18n Key Generation for Large Projects

Large-scale applications with 5,000+ translation keys and multiple development teams face unique challenges in i18n key management. A systematic approach to key generation becomes essential to prevent chaos.

Scale-Related Challenges

1. Key conflicts -- multiple teams adding keys to the same namespace
2. Inconsistent naming -- different teams using different conventions
3. Missing translations -- new keys added in one locale but not others
4. Orphaned keys -- keys remaining after features are removed
5. Performance -- loading thousands of keys in a single bundle

Team-Based Namespace Strategy

Assign namespace ownership to teams:

Team A (Auth):
  auth.login.*
  auth.signup.*
  auth.password_reset.*

Team B (Dashboard):
  dashboard.overview.*
  dashboard.analytics.*
  dashboard.settings.*

Team C (Checkout):
  checkout.cart.*
  checkout.payment.*
  checkout.confirmation.*

Shared (Design System team):
  common.buttons.*
  common.labels.*
  common.errors.*
  common.status.*

Code Splitting Translations

For performance, split translation files by route or feature:

locales/
  en/
    common.json     (50 keys, loaded on every page)
    auth.json       (100 keys, loaded on /login, /signup)
    dashboard.json  (200 keys, loaded on /dashboard/*)
    checkout.json   (150 keys, loaded on /checkout/*)

Only common.json is in the initial bundle. Other namespaces load dynamically.

Batch Key Generation Workflow

For large-scale extraction:

1. Extract -- Use a script to find all hardcoded strings in components
2. Categorize -- Run strings through the i18n Key Generator in batch mode
3. Review -- Team leads review generated keys for accuracy
4. Merge -- Combine generated keys with existing translation file
5. Translate -- Send new keys to translation management system
6. Validate -- CI checks for completeness across all locales

Monorepo Considerations

In monorepos with multiple apps sharing translations:

packages/
  i18n/
    common/       (shared across all apps)
      en.json
      ja.json
    app-web/      (web app specific)
      en.json
      ja.json
    app-mobile/   (mobile app specific)
      en.json
      ja.json

Key Versioning

For large projects, consider versioning translation keys:

• Add new keys with new names instead of modifying existing ones
• Mark deprecated keys with a prefix (_deprecated.old_key)
• Run cleanup scripts quarterly to remove deprecated keys
• Keep a changelog of key additions, modifications, and removals

Metrics to Track

• Total keys per locale
• Translation completion percentage per locale
• Keys added/removed per sprint
• Unused key count
• Average key depth (should stay under 4)