Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The next-i18next config file

To configure next-i18next, a config file is required. In the project folder, create a new file and name it next-i18next.config.js .

List the locales in an array, and list the defaultLocale.

module.exports = {
  i18n: {
    // all the locales supported in the application
    locales: ['en-GB', 'en-US'], 
    // the default locale to be used when visiting
    // a non-localized route (e.g. `/about`)   
    defaultLocale: 'en-GB',
  },
}

We will then set the fallback language. This is so if we can not provide the preferred language for a user, we can specify another language as fallback.

module.exports = {
  i18n: {
    // all the locales supported in the application
    locales: ['en-GB', 'en-US'], 
    // the default locale to be used when visiting
    // a non-localized route (e.g. `/about`)   
    defaultLocale: 'en-GB',
  },

  fallbackLng: 'en-GB',
}

We will then follow the same pattern for the namespaces. Stating the namespaces here allows us to use multiple files within a locale to access translations.

module.exports = {
  i18n: {
    // all the locales supported in the application
    locales: ['en-GB', 'en-US'], 
    // the default locale to be used when visiting
    // a non-localized route (e.g. `/about`)   
    defaultLocale: 'en-GB',
  },

  fallbackLng: 'en-GB',
  
  ns: ['common', 'application', 'validation'],
  defaultNS: 'application',
  fallbackNS: 'common',
  • No labels