What problem does it solve?
ZERO hardcoded user-visible text and inconsistent locale handling by providing standardized i18n patterns, translation structure, and SSR-safe initialization.
Core Features & Use Cases
- Establishes a flat, domain-prefixed translation key framework (common., validation., errors.*) with TypeScript typings.
- Defines locale detection order (user preference, URL, subdomain, Accept-Language, navigator.language) and CLDR-aware pluralization and formatting.
- Integrates error translation for Zod form validation and API errors, route metadata, and SEO titles to ensure fully translated UIs.
Quick Start
Implement the i18n pattern by replacing plain strings with t() calls, wiring up the locale detector, and mapping errors to translation keys.