@spfn/i18n supplies the small runtime between your translation catalogs and your UI: interpolation, fallback lookup, server helpers, and React context. Your application keeps ownership of the words and the locale policy.
A second language is cheap to allow for early and expensive to retrofit once the copy is scattered through components.
Catalog loading, persistence, and content stay in the consuming application, and so does the locale policy: localized routing and negotiateLocale are helpers the app chooses to call, never a default the runtime imposes. The runtime accepts plain locale → namespace → message objects and turns them into predictable translators without imposing a file layout, fetch layer, or CMS.
getClientMessages() resolves selected namespaces on the server, merging fallback values first and locale-specific values second. Pass the serializable result through I18nProvider; client components call useT() without a loading flash or a second catalog request.
Locale, namespace, key, message — application-owned objects.
Translate independently of React, Next.js, or SPFN.
Named string and number placeholders remain visible when missing.
Locale-specific values override a configured fallback locale.
Configure once, then resolve namespace-scoped translators.
Serialize only selected, fully resolved namespaces.
I18nProvider, useT, and useLocale for client subtrees.
Register the catalog shape once and a mistyped key fails the compile.
A translator that takes the namespace from the key — useT() and getT(locale).
onMissingKey fires when neither the locale nor the fallback has an entry.
defineI18nRouting — a URL policy such as English at / and Korean at /ko.
negotiateLocale and localeCookie for app screens with no locale in the URL.
No catalog loaders, date or number formatting, or plural rules.