Support for 'default' locale

[nhac-lly]

https://nextjs.org/docs/advanced-features/i18n-routing#prefixing-the-default-locale
as NextJS team suggest, it is better to use 'default' that fallback to actual main language for some case.
One of those case is to have locale routing always on URL.

For now to use it I need to create a local file for 'default'.
Can we somehow map it to 'en'?

[isaachinman]

Sorry, I don't think I understand your question. Can you explain further?

[nhac-lly]

module.exports = { i18n: { locales: ['default', 'en', 'de', 'fr'], defaultLocale: 'default', localeDetection: false, }, trailingSlash: true, }
I meant when using this config, you need to also create a public/locale/default/common.json for the 'default' locale, but 'default' is just to fallback to the actual language like 'en'.
In other word is to force 'default' to not needing a locale json for it as it is not used.

[isaachinman]

Ah OK, got it. I'm not convinced that using a non-standard "locale" like default just to manipulate routing is a good idea in the first place. It speaks to the lack of configurability on the NextJs routing side of things.

That being said, I would be fine with merging support for this, as it is indeed in the official NextJs docs, for better or worse. We would need to update createConfig to ignore non-standard locales. PRs welcome.

[fcandi]

Thanks, I am in the same boat, using the "default" language as recommended in the official docs, forwarding "/" to "/some_locale" depending on the browsers language.

I now get an ENOENT error loading the non existing default language. Is there a simple preliminary fix for now?

Andreas

[santyas]

Hey @fcandi @nhac-lly

I've tested it, first you have to create default folder inside /public/locales/ with a common.js file inside (I think that it works if its empy, if it crash just duplicate this common.js file as your common.js prefered locale default).

Then update your getStaticsProps func:

export const getStaticProps: GetStaticProps = async ({locale}) => {
  let theLocale = locale as string
  console.log(`Locale: ${theLocale}`)

  return {
    props: {
      ...(await serverSideTranslations(theLocale == 'default' ? 'ar' : theLocale, ['common'])),
    },
  };
}

I'm using TS so I had to edit it a little bit.

Keep in mind you must have the _middleware file configured as specified in the nextjs i18n docs.

My next.config file:

const {i18n} = require('./next-i18next.config');

const nextConfig = {
	reactStrictMode: true,
	i18n,
	trailingSlash: true,
}

module.exports = nextConfig

And my next-i18next.config file:

module.exports = {
	i18n: {
		locales: ['default', 'ar', 'uy', 'bo', 'py'],
		defaultLocale: 'default',
		localeDetection: false,
	},
};

CC @isaachinman

[adrai]

Support for Prefixing the Default Locale will be included in the next release.

[adrai]

included in v11.1.1

[deltasierra96]

included in v11.1.1

Any documentation on this feature or is it as before?

[adrai]

there is no extra config needed. it just ignores the language "default" when configured in the i18n config: f9a6539#diff-28136a2e354d423cb0c0191cef90624f802ee7921bf0aacbb9bfd3e5f2b1f501R226

[deltasierra96]

there is no extra config needed. it just ignores the language "default" when configured in the i18n config: f9a6539#diff-28136a2e354d423cb0c0191cef90624f802ee7921bf0aacbb9bfd3e5f2b1f501R226

Awesome. Thanks for the update, Adraino!