next-intl Internationalization Patterns

Quick Guide: useTranslations renders messages, useFormatter renders dates, numbers and lists, and createMiddleware detects the locale. setRequestLocale(locale) at the top of a page or layout is what keeps it statically renderable. v4.0+ registers types through the AppConfig interface and sets the locale cookie only when the user switches away from their Accept-Language preference. Every pattern here is App Router — the Pages Router integration is a separate API and none of this transfers to it.

Detailed Resources:

• examples/core.md — setup, provider, useTranslations, plurals, formatting, static rendering, locale switching, types
• examples/formatting.md — relative time with auto-update, list formatting, combined format patterns
• examples/pluralization.md — ordinals, plural nested in select, zero-case handling
• examples/markup.md — t.markup() for HTML strings: email bodies, feeds, sanitisation
• reference.md — decision trees, anti-pattern code, ICU syntax tables, setup checklists