npm next-i18next 16.4.6
v16.4.6

3 hours ago
  • Interpolation options no longer turn HTML escaping back on - next-i18next turns i18next's escaping off (interpolation: { escapeValue: false }, React escapes text itself), but it set that as a whole interpolation object and spread the user's options over it. Any interpolation option (prefix/suffix, defaultVariables, ...) in i18nextOptions of the App Router server config or I18nProvider (also the ICU and MF2 providers), or in the Pages Router config, dropped it. i18next then escaped every value and React escaped it again, so O'Brien & Co rendered as O'Brien & Co and 1/2/2026 as 1/2/2026. The user's interpolation options are now merged into the default, and escapeValue: true still turns escaping on. Apps that set interpolation options and render translations as HTML (dangerouslySetInnerHTML) lose that accidental escaping; set escapeValue: true to keep it. Thanks @nk-batman21 (#2354)

Don't miss a new next-i18next release

NewReleases is sending notifications on new releases.