next-intl

What problem does it solve?

next-intl removes the guesswork of wiring i18n in a Next.js monorepo by providing a consistent, locale-aware pattern for routing, message loading, and typed navigation across both the customer PWA and admin CRM.

Core Features & Use Cases

• Consistent locale routing in App Router: Defines locales, default locale, locale prefix behavior, and translated public URLs via a shared routing convention.
• Automatic language detection and redirects: Uses middleware-style request interception to select the best locale using cookie and Accept-Language, then redirects while keeping a stable NEXT_LOCALE cookie.
• Typed navigation that prevents wrong-locale links: Replaces raw next/link and next/navigation imports in localized routes with a typed wrapper from '@/i18n/navigation' to avoid silent misrouting.
• Server/client translation APIs with correct request scoping: Supports server components via getTranslations and client components via useTranslations, with guardrails to preserve static rendering behavior.
• Route and metadata localization: Handles translating routes through the pathnames map and localizing generateMetadata using explicit locale input.

Quick Start

Use the next-intl skill to onboard a teammate by walking them through where messages live, how NEXT_LOCALE is detected, and how to translate a new route without breaking locale-aware navigation.