Today I released
version 1.4.0 of
next-export-i18n, the i18n module for Next.js which is fully compatible with
$ npm i next-export-i18n or get
next-export-i18n v1.3.0 from npm.js.
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.
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
This npm module provides a simple solution for Internationalization (i18n) of projects using
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
Next.js i18n-routing does not supports
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-i18n provides a simple solution for Internationalization (i18n) when you want to generate a truly static website with
Read the Introduction to
next-export-i18n - next.js: i18n with static sites for more details.
You can also take a look at the example implementation next-export-i18n-example.vercel.app and its source code at github:
- next.js: i18n with static sites (Introduction)
- Example implementation: https://next-export-i18n-example.vercel.app
- Github for the npm-module: https://github.com/martinkr/next-export-i18n
- Github for the example: https://github.com/martinkr/next-export-i18n-example