next-export-i18n v1.4.0: make the user's default language optional

Today I released version 1.4.0 of next-export-i18n, the i18n module for Next.js which is fully compatible with next export.

Install next-export-i18n with $ npm i next-export-i18n or get next-export-i18n v1.3.0 from npm.js.

New feature: Making the user's default language optional

Starting with Version 1.4.0, next-export-i18n reads the user's default language settings from the browser. If this language is available as i18n it is automatically used as the default language. As long as you do not disable it.

The config-file has an additional option useBrowserDefault now. Set this to false to forcefully overwrite the browser's default language with the one set in the config.

About `next-export-i18n`

This npm module provides a simple solution for Internationalization (i18n) of projects using next export.

Next.js already has support for internationalized (i18n) routing out-of-the-box. You can provide a list of locales, a default as well as domain-specific locales and Next.js automatically handles the routing. It streamlines the touring and locale parsing for nearly all existing l18n library solutions available for Next.js such as react-intl, react-i18next, lingui, rosetta, next-intl.

Unfortunately, Next.js i18n-routing does not supports next export.
This means that none of the i18n-libraries (which are utilizing the build in i18n-routing) is able to support fully static sites which are generated with next export.

next-export-i18n provides a simple solution for Internationalization (i18n) when you want to generate a truly static website with next export.

Read the Introduction to next-export-i18n - next.js: i18n with static sites for more details.