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 GitHub upstream push on 2026-10-02 and a steady stream of tagged updates from late August through early October (v4.14.1 to v4.14.9) indicate ongoing maintenance rather than a dormant period.
- Apparent update cadence: Roughly every few days to about weekly, with multiple small patch updates during September, culminating in v4.14.9 on 2026-10-02.
AI summary generated
Recent updates
v4.14.9
v4.14.9 primarily addresses source map related issues in the `useExtracted` extraction flow. The release notes only mention this as a bug fix, and the code changes confirm modifications around how source maps are produced and passed through the extractor/loader.
v4.14.8
v4.14.8 fixes message extraction ordering for `useExtracted` when multiple messages occur on the same source line. The diff shows the fix is implemented by capturing a character-level `column` for each extracted reference and then using it to break ties. Release notes mention the behavioral fix, but not the underlying metadata and related dependency updates.
v4.14.7
Release v4.14.7 is a small metadata-only update focused on TypeScript/typing compatibility. It adds an optional `@types/react` peer dependency to relevant packages to better support setups that use global or virtual package manager stores.
v4.14.6
v4.14.6 is a small patch release focused on the SWC extractor plugin for next-intl. It updates the plugin to include source ranges for `useTranslations` key references.
v4.14.5
v4.14.5 is a small bug fix release focused on preventing Next.js Cache Components issues by avoiding reads of the current pathname in `useRouter` and locale-changing `Link` logic. The implementation changes more than just that, including how the locale cookie base path is computed and which inputs are used for cookie syncing.
Breakingv4.14.4
v4.14.4 is a patch release focused on improving base path detection used when setting cookies. The code change refines how `getBasePath` derives the cookie base path from the current pathname and adds test coverage for edge cases.
v4.14.3
v4.14.3 ships a targeted routing-related fix: route param values containing `$`-patterns are now kept literally instead of being interpreted by JavaScript `String.replace` as replacement tokens. The change is implemented in both pathname template formatting and localized pathname compilation, with new regression tests added.
v4.14.2
Release v4.14.2 is a small maintenance update. The core change is dependency range updates for the internal @eloqnt/* packages so patch releases can resolve correctly.
v4.14.1
v4.14.1 contains a targeted bug fix intended to prevent Turbopack from failing validation when `experimental.messages` is missing `messages.sourceLocale`. The code change ensures that loader option objects do not contain `undefined` values when passed to Turbopack loaders.
v4.14.0
v4.14.0 focuses on improving `useExtracted`, specifically supporting destructuring from `Promise.all` in the extractor/compiler. The release notes also warn that using `useExtracted` with `.po` catalogs requires updating messages, with a pointer to the relevant PR for the migration details.
BreakingFeaturesv4.13.7
Release v4.13.7 mainly updates dependency constraints to address compatibility between the extractor plugin and @swc/core. The diff also includes a monorepo version bump to 4.13.7 and several test/example dependency bumps, most notably Next.js.
v4.13.6
Release v4.13.6 is primarily a maintenance update. The documented change is that `requestLocale` is deprecated for the `getRequestConfig` callback, aligning with Next.js `next/root-params` usage.
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.