Translate JavaScript and TypeScript locale files with Hyperlocalise

​

Source file

export default {
    home: {
        title: "Welcome",
        greeting: "Hello, {name}!",
    },
} as const;

​

Configure your files

locales:
    source: en-US
    targets:
        - es-ES

buckets:
    messages:
        files:
            - from: locales/en-US/messages.ts
              to: locales/{{target}}/messages.ts

llm:
    profiles:
        default:
            provider: openai
            model: gpt-5.2

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Supports static locale objects exported with export default, export const, or module.exports, including a static variable followed by a default export.
• Nested objects and string arrays are supported. Strict FormatJS message objects can include defaultMessage and description.
• Imports, comments, export syntax, and unrelated module text are preserved. Only message string literals are replaced.
• Dynamic values, computed keys, spreads, multiple exported locale objects, and interpolated template literals are rejected. These are locale modules, not arbitrary application source files.

​

Next steps

• Check translations before committing generated files.
• Local translation workflow explains repeat runs.
• Browse all file formats.

​

Related formats

• JSON localization
• FormatJS and React Intl catalogs