- update some i18next dependencies to address #2288
- Only overwrite ns config if it provided #2270
- add possibility to pass resources directly via config and set localePath to null
- fix: Install error with react-i18next v14 #2248
- optimize/fix last change for turbo
- try to fix for turbo #2222
- refactor: reuse existing i18next instance #2226
-> If you use client side pages (not lazy loading translations), like described here, make sure you set the
partialBundledLanguages
option to true, like here.
- fix: correct namespacesRequired type in serverSideTranslations #2203
- try to fix namespacesRequired in serverSideTranslations is not type-safe anymore #2201
- requires i18next >= v23.0.1
- requires react-i18next >= v13.0.0
i18next 23.0.0 dropped support for older browsers. From nextjs 13, you can use the transpilePackages to avoid issues.
/** @type {import('next').NextConfig} */
const nextConfig = {
transpilePackages: ['i18next'],
}
module.exports = nextConfig
- using a custom backend on server side should also lazy load the passed namespaces
- pageProps may be undefined on strange setups #2109"
- types: fix serverSideTranslations args #2104"
- types: Update serverSideTranslation args type #2097"
- fix: allow user provided affixes to be used without providing localeStructure #2100"
- revert #2084
- another code snippet for #2084 to try to fix for dynamic pages
- different code snippet for #2084 to try to fix for dynamic pages
- log config path if no config found
- feat(server-side): custom default config path #2084
- Error if custom localeStructure provided, but no ns option defined.
- Types: DefaultNamespace import, see #2061.
- Fix missing
i18n.localeDetection
in UserConfig, see #2057. - Update examples to latest i18next in #2058
Caution
If you're experiencing typecheck errors regarding keys: ensure i18next
is at least ^22.4.3
in your
package.json (then run install), see #2058.
The v13.0.0 release is a major version to improve stability and general experience. It comes with 2 easy changes related to installation. Existing code shouldn't be impacted. Details can be found in the UPGRADING.md document.
-
react-i18next and i18next have been moved to peer-dependencies. They must be installed in your app (#1966)
# Add react-i18next > 12.0.0 and i18next > 22.0.4 to your app dependencies npm install react-i18next i18next --save # NPM yarn add react-i18next i18next # Yarn pnpm add react-i18next i18next --save # PNPM
This might solve issues with duplicates and multiple i18n context instances. If you encounter any issue, please read the Troubleshoot doc before posting an issue.
-
Types augmentations are now handled by i18next instead of react-i18next (#1997). See the upgrade document here.
- Support for NextJs 13 (excluding new experimental layout / rsc)
- Upgrade to i18next v22 and react-i18next v12, see #1966
- Support for node 18 lts #2017
- Fix types for appWithTranslation #1987
We've dropped support for nextjs < 12.0.0 / react < 17.0.2 (#1983) and node < 14 (#1974).
- fix: appWithTranslation re-renders _app when the locale is changed (#1954)
- feat: introduce onPreInitI18next option (#1960)
- fix: fallbackLng if namespaces are undefined (#1943 closes #1941)
Why a major version? The following changes could lead to more languages being loaded, which could increase the page size.
- feat: improve fallback language handling (#1927)
- feat: add support for nonExplicitSupportedLngs (#1930)
- feat: introduce extraLocales (#1916)
- fix: pass namespaces to the client also for custom backends (#1913)
- fix: pass namespaces to the client (#1912 closes #1839)
- feat: support nested namespace structure (#1911)
- fix: remove postinstall script
- first release with new project ownership
- update most dependencies
- update docs and example
- feat: support default locale by ignoring it (#1679)
Features:
- Allow client side translation loading (8132efd)
Documentation:
- Link to
react-i18next
config options (422a0f3)