Next.js i18n · TypeScript
Palamedes gives Next.js 16 one translation model across Server Components, Client Components, and server actions. The Next plugin handles macro transforms and catalog loading; your application keeps control of routing and locale policy.
One host adapter for macro transforms and PO imports.
App Router with the current Turbopack path.
Server Components, Client Components, and server actions.
Cookie, route, subdomain, and top-level domain.
@palamedes/next-pluginv1.17.35.9K downloads / month01 — The framework problem
A locale segment or cookie is only the first decision. Translations must resolve to the same locale while React crosses server and client boundaries, streams HTML, hydrates the browser, and runs a server action later.
02 — The Palamedes model
Palamedes treats Next.js as a host, not as a separate translation architecture. The adapter owns the build integration while the core keeps message identity, catalogs, diagnostics, and runtime access consistent.
withPalamedes() transforms TypeScript macros and compiles imported PO catalogs for Turbopack, with webpack available as a fallback.
A server-only scope binds getI18n() to the active request so downstream Server Components and actions use the right locale.
Write t and Trans next to the component. Server and client code share source-string-first catalogs instead of maintaining parallel APIs.
03 — In TypeScript
next.config.ts + app/page.tsx
// next.config.ts
import { withPalamedes } from "@palamedes/next-plugin"
export default withPalamedes({})
// app/page.tsx — a Server Component
import { t } from "@palamedes/core/macro"
import { createActiveServerI18n } from "@/lib/i18n.server"
export default async function Page() {
await createActiveServerI18n()
return <h1>{t`Welcome to Palamedes`}</h1>
}The server helper resolves the locale, loads its catalog, and activates a request-local scope once. The checked example also initializes the client boundary and verifies a localized server action.
04 — Locale strategy
Next.js owns URL structure and request handling. Palamedes supplies typed locale controls and the same catalog runtime for all four patterns, so choosing an SEO-friendly route segment does not require choosing a different translation library.
One URL for all locales. Best for apps behind login where SEO is irrelevant and switching should be instant.
/de/checkout-style paths. The SEO-friendly default for public content with indexable localized pages.
de.example.com. Clean separation per market, works well with regional CDNs and analytics splits.
example.de vs example.com. Maximum market trust; Palamedes maps each domain to its locale.
◌ local / CIsource →
05 — Proof and boundaries
The Next.js family is part of the repository's browser-verification matrix. The checks start the application, inspect server-rendered output, switch locale, and invoke translated server behavior.
The expected locale is present before hydration.
Copy, plurals, dates, and currency move together.
A server action returns localized output after interaction.
Examples, verifier, and screenshots are checked in.
06 — Questions
The short version of the decisions that usually block an implementation.
07 — Keep exploring