rsnext/test/integration/i18n-support-catchall/next.config.js

module.exports = {
  // target: 'experimental-serverless-trace',
  i18n: {
    locales: ['nl-NL', 'nl-BE', 'nl', 'fr-BE', 'fr', 'en-US', 'en'],
    defaultLocale: 'en-US',
  },
}
Ensure params and locale are parsed correctly in fallback mode (#19063) This fixes a few things related to optional catch-all routes and i18n. The first thing is it ensures the correct data route is generated on the client so that the locale isn't duplicated for an optional catch-all route, the next is it ensures the browser history is updated correctly when only a locale change is occurring, and then it also ensures we handle the locales and normalizing for fallback optional catch-all pages correctly. Tests have been added to ensure these cases are covered properly and we don't regress on them, these changes were also tested on Vercel [here](https://next-js-bug-i18n-root-params-nybg44l0b.vercel.app/) Fixes: https://github.com/vercel/next.js/issues/18633 Fixes: https://github.com/vercel/next.js/issues/19059 2020-11-11 21:33:44 +01:00			`module.exports = {`
			`// target: 'experimental-serverless-trace',`
			`i18n: {`
			`locales: ['nl-NL', 'nl-BE', 'nl', 'fr-BE', 'fr', 'en-US', 'en'],`
			`defaultLocale: 'en-US',`
			`},`
			`}`