next-i18next-static-site
i18next solution for static sites build with Next.js (static HTML export / next export).
This package brings you `react-i18next` and `i18next` to your static sites build with the `next export` future from Next.js.
- 🗲 Translation is already rendered (SSG), client will receive the final translated site.
- 🔥 Hot reloading works also when you update your locale (translation) files.
- 🚀 Automatic browser language detection can be realized.
- 🍪 Cookie stores the client language.
## Installation
```
npm install --save next-i18next-static-site
```
## Usage
> `publicRuntimeConfig` is deprecated by Next.js.
> I moved the configuration for `next-i18next-static-site` to environment variables.
Set the supported languages and the namespaces in your `next.config.js` or in your `.env.local`:
`next.config.js` example:
```js
module.exports = {
env: {
NEXT_PUBLIC_I18N_LANGUAGES: '["en", "de"]',
NEXT_PUBLIC_I18N_DEFAULT_LANGUAGE: "en",
NEXT_PUBLIC_I18N_NAMESPACES: '["common", "meta", "error"]',
NEXT_PUBLIC_I18N_DEFAULT_NAMESPACE: "common",
},
};
```
Arrays have to be a string within `next.config.js`, just put them into brackets, otherwise Next.js will throw an error.
`.env.local` example:
```
NEXT_PUBLIC_I18N_LANGUAGES=["en", "de"]
NEXT_PUBLIC_I18N_DEFAULT_LANGUAGE=en
NEXT_PUBLIC_I18N_NAMESPACES=["common", "meta", "error"]
NEXT_PUBLIC_I18N_DEFAULT_NAMESPACE=common
```
Additional [i18next options](https://www.i18next.com/overview/configuration-options) can be set with `NEXT_PUBLIC_I18N_OPTIONS`:
> Note:
> Calling functions like `parseMissingKeyHandler` won't work within the .env file, use