npm next-i18next 16.4.2
v16.4.2

4 hours ago
  • Pages Router: translations load on the server again with a custom interpolation.prefix / suffix - localeStructure and the server loadPath are built from the configured prefix and suffix (e.g. {lng}/{ns}), but the file loader that replaced i18next-fs-backend in 16.0.0 only replaced {{lng}} and {{ns}}. It tried to read a literal public/locales/{lng}/{ns}.json, the error only showed with debug: true, and serverSideTranslations returned empty namespaces, so pages rendered the raw keys. The loader now uses the same prefix and suffix as the config. The default config and a function localePath are unchanged. Thanks @nk-batman21 (#2350)

Don't miss a new next-i18next release

NewReleases is sending notifications on new releases.