next-intl provides internationalization (i18n) tools for Next.js, including ICU message syntax for translations and formatting for dates, times, and numbers. It also offers a hooks-based API for turning translation messages into plain strings or rich text, with type-safe message key support. It is useful for building language-aware React apps, including internationalized routing.
Project status
- Actively maintained: Yes. The repo shows frequent updates in 2026, including a recent upstream push on 2026-07-29, and multiple version updates in late July and June.
- Update cadence: Appears steady and fairly responsive, with several updates clustered in July 2026 (for example, 4.13.1 to 4.13.4 between 2026-06-30 and 2026-07-23), suggesting an active development and fix pipeline rather than long quiet periods.
AI summary generated
Recent updates
v4.13.5
Release v4.13.5 primarily updates the documentation and blog content around Next.js `next/root-params`, along with deprecating `setRequestLocale`. The code changes visible in this diff are minimal and mostly affect internal API deprecation signaling, plus contributor-facing release workflow automation.
v4.13.4
v4.13.4 is a small bug-fix release focused on Next.js partial prefetching behavior. It refactors the internal Link implementation so `usePathname()` is not read for links that do not switch locales, avoiding unnecessary `<Suspense>` involvement in certain configurations.
v4.13.3
v4.13.3 is a small release focused on preparing next-intl for Next.js 16.3 behavior around locale cookies. The provided diff shows mostly documentation and website changes, plus new e2e test fixtures intended to validate locale cookie behavior for document requests and partial prefetching.
v4.13.2
v4.13.2 is a targeted bug fix release. It improves plural/select handling when the selected branch content is effectively empty (for example, branches that are only '#' or empty braces).
v4.13.1
v4.13.1 is primarily a bug fix release. It updates the message compilation fast path logic so ICU escape sequences involving '<' are handled consistently between development and production, and adds a regression test to cover the production behavior.
v4.13.0
v4.13.0 changes how next-intl auto-generates message IDs for extraction by switching from standard base64 to URL-safe base64 (no padding). Release notes state this affects `useExtracted` and that existing keys must be updated accordingly. The code diff indicates the ID generation change is applied at the extractor/plugin level, which can impact auto-generated IDs in broader extraction workflows.
BreakingFeaturesv4.12.0
v4.12.0 focuses on improvements around `useExtracted`. The release notes only call out a small required configuration change for `useExtracted` users, but the code diff shows deeper changes in the extraction pipeline and the shape of extracted metadata that can affect generated catalogs and any consumers depending on that metadata.
BreakingFeaturesv4.11.2
Release v4.11.2 is a small bug fix release that reverts a prior change related to using the proxy header x-forwarded-host for redirect domain behavior in next-intl middleware. The code change specifically alters how the middleware chooses the redirect host, protocol, and port when constructing redirect URLs.
v4.11.1
v4.11.1 is a small patch release that targets Next.js telemetry behavior, specifically preventing watcher startup when Next runs its detached telemetry flush process. The code change is implemented via runtime detection in the Next.js plugin initialization path, and the diff also includes multiple extractor-related test updates and internal refactoring signals.
v4.11.0
v4.11.0 adds support for formatting locale-aware display names via a new `displayName` function on the `useFormatter` hook. The change includes TypeScript typing for global formats (`formats.displayName`) and updates documentation and tests to cover `Intl.DisplayNames` usage.
Featuresv4.10.1
v4.10.1 is a small bug fix release focused on how next-intl middleware builds redirect URLs when running behind a reverse proxy. It now uses the `x-forwarded-host` header to determine the redirect host, and uses `x-forwarded-proto` and `x-forwarded-port` to set the protocol and port.
v4.10.0
v4.10.0 adds support for overriding the global `localePrefix` behavior on a per-domain basis. The change affects routing configuration types, middleware redirect/rewrite decisions, link generation (alternate links), and client navigation pathname prefixing logic.
Featuresv4.9.2
v4.9.2 is presented as a bug fix release addressing prototype-safety issues when using `precompile: true`. The code diff shows broader prototype-hardening changes across message extraction, catalog precompilation, and ICU message compilation, aiming to prevent prototype pollution and prototype-key collisions.
BreakingSecurityv4.9.1
v4.9.1 is a patch release with a single documented bug fix: improving middleware pathname validation. The code changes primarily focus on hardening how middleware sanitizes incoming pathnames to prevent malicious URL/path parsing edge cases that can lead to open redirects.
v4.9.0
v4.9.0 adds support for the `transitionTypes` prop on `Link`. In the codebase, this is implemented via TypeScript prop typing changes in the shared navigation Link wrapper, and the repo also bumps Next.js and React type dependencies used by examples and tooling.
Features