npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

i18n-email

v0.2.0

Published

Translate transactional emails into any language using AI models.

Downloads

308

Readme

i18n-email

Translate transactional emails into any language using AI models. Works with React Email components or raw HTML. Automatically detects the source language and skips translation when the email is already in the target locale.

Features

  • Accepts a React Email component or a raw HTML string
  • Translates the subject line and body in a single OpenAI call
  • Batches large emails — splits strings into chunks to stay within model limits
  • Skips <style>, <script>, and <head> — only visible text is sent
  • Injects dir="rtl" automatically for Arabic, Hebrew, Persian, Urdu, and more
  • Optional cache layer with a key prefix to avoid redundant API calls
  • onTranslate hook for logging and analytics
  • Supports any OpenAI-compatible API via baseURL

Install

bun add i18n-email
# or
npm install i18n-email

Requires react >= 18 as a peer dependency.

Usage

With a React Email component

import { createI18nEmail } from "i18n-email";

const i18nEmail = createI18nEmail({
  openaiApiKey: process.env.OPENAI_API_KEY!,
});

const { subject, html } = await i18nEmail.translate({
  locale: "pl",
  subject: "Welcome!",
  react: <WelcomeEmail name="Dan" />,
});

With raw HTML

const { subject, html } = await i18nEmail.translate({
  locale: "ar",
  subject: "Welcome!",
  html: "<h1>Welcome!</h1><p>Your account has been created.</p>",
});

With caching (Upstash Redis example)

import { Redis } from "@upstash/redis";

const redis = Redis.fromEnv();

const i18nEmail = createI18nEmail({
  openaiApiKey: process.env.OPENAI_API_KEY!,
  cache: {
    prefix: "i18n-email:",
    get: async (key) => {
      const value = await redis.get(key);
      if (value === null) return null;
      return typeof value === "string" ? value : JSON.stringify(value);
    },
    set: async (key, value) => {
      await redis.set(key, value);
    },
  },
});

With logging

const i18nEmail = createI18nEmail({
  openaiApiKey: process.env.OPENAI_API_KEY!,
  onTranslate: ({ locale, detectedLocale, strings, cacheHit }) => {
    console.log(
      `Translated ${strings.length} strings to ${locale}` +
        ` (detected: ${detectedLocale}, cache: ${cacheHit})`,
    );
  },
});

API

createI18nEmail(config)

| Option | Type | Default | Description | | -------------- | --------------------------------------- | ---------- | --------------------------------------------- | | openaiApiKey | string | — | OpenAI API key | | model | string | "gpt-4o" | Any OpenAI chat model | | baseURL | string | — | Override the API base URL (Azure, Groq, etc.) | | maxRetries | number | 2 | Retries on transient OpenAI errors | | batchSize | number | 50 | Max strings per OpenAI request | | cache | CacheProvider | — | Cache adapter to avoid redundant API calls | | onTranslate | (info: TranslateCallbackInfo) => void | — | Hook called after every translate call |

Returns { translate }.

translate(options)

| Option | Type | Required | Description | | --------- | -------------- | -------- | --------------------------------------------- | | locale | string | Yes | Target locale (e.g. "pl", "ar") | | subject | string | Yes | Email subject line | | react | ReactElement | One of | React Email component to render and translate | | html | string | One of | Raw HTML string to translate |

Returns Promise<{ subject: string; html: string }>.

If the email is already in the target locale, the original subject and html are returned unchanged. Locale matching normalizes base tags, so "en-US" and "en" are treated as the same language.

CacheProvider

interface CacheProvider {
  prefix?: string;
  get: (key: string) => Promise<string | null>;
  set: (key: string, value: string) => Promise<void>;
}

The cache key is a SHA-256 hash of the HTML, subject, and locale. prefix is prepended to every key when provided.

TranslateCallbackInfo

interface TranslateCallbackInfo {
  locale: string; // requested target locale
  detectedLocale: string; // source locale detected by OpenAI
  strings: string[]; // all strings sent for translation (empty on cache hit)
  cacheHit: boolean; // true when the result was served from cache
}