Waku i18n · React Server Components
Palamedes keeps translation state aligned across Waku's React Server Component tree and its hydrated client islands. A Vite adapter transforms messages; the shared runtime resolves the active catalog on the correct side of the boundary.
Configured inside Waku's Vite plugin surface.
React 19 Server Components on beta.6.
Server-first pages with hydrated client boundaries.
Cookie, route, subdomain, and top-level domain.
@palamedes/wakuv1.17.3677 downloads / month01 — The framework problem
Waku begins with a Server Component tree, then introduces client boundaries only where interactivity is needed. Locale state must be available in both environments without shipping server machinery to the browser or rendering two languages during hydration.
02 — The Palamedes model
Palamedes keeps the environment-specific activation explicit while sharing authoring, catalogs, ICU semantics, and diagnostics across the RSC boundary.
Add the Palamedes transform through Waku's vite.plugins configuration beside the React plugin already used by the application.
Resolve the request locale and activate a fresh i18n instance before the Server Component page calls t or Trans.
Only interactive islands load the React client helpers. Server-rendered translated content does not require turning the whole page into a Client Component.
03 — In TypeScript
waku.config.ts + pages/[locale].tsx
// waku.config.ts
import react from "@vitejs/plugin-react"
import { defineConfig } from "waku/config"
import { palamedes } from "@palamedes/vite-plugin"
export default defineConfig({
vite: {
plugins: [
palamedes(),
react(),
],
},
})
// pages/[locale].tsx — a Server Component
import { t } from "@palamedes/core/macro"
export default async function LocalePage() {
return <h1>{t`Welcome to Palamedes`}</h1>
}The checked example resolves and activates the request locale before rendering this page, then initializes only the interactive client components with the same catalog.
04 — Locale strategy
Waku decides how pages map to URLs and requests. Palamedes keeps the RSC and client translation model fixed while the matrix changes where the locale is detected and how a switch is represented.
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
Waku has its own browser-verified example family. It is not counted as proof merely because the Next.js adapter also supports Server Components.
Translated output is rendered in the server-first page.
Interactive translated components hydrate and switch.
Host and path decisions are verified separately.
Three hosted strategies plus the checked TLD source.
06 — Questions
The short version of the decisions that usually block an implementation.
07 — Keep exploring