[i18n] redirects defined in next.config.js doesn't work on Vercel

[dmitrykozyrenko]

Bug report

Describe the bug

redirects defined with i18n config in next.config.js doesn't work when deploying to Vercel, but work in dev.

Expected behavior

redirects with i18n should work when deploy to Vercel.

System information

• OS: Windows
• Browser: Chrome
• Version of Next.js: 10.0.1
• Version of Node.js: 12.16.1

[fpahl]

I am experiencing the same issue with next.js 10.0.1.

[dohomi]

I am facing the same issue on 10.0.1. redirects work fine on localhost but not deployed via Vercel

[ijjk]

Hi, this has been updated in the latest canary of Next.js v10.0.2-canary.17, docs for the new redirects + i18n handling can be viewed here until a new patch release is published, please upgrade and give it a try!

[dmitrykozyrenko]

@ijjk thank you! But in Next.js v10.0.2-canary.17 defaultLocale is ignored.

For example If we have i18n config
{ locales: ['en', 'fr', 'zh'], defaultLocale: 'en' }

and redirect like this one
{ source: '/first-page', destination: '/second-page', permanent: true }

we will be redirected from /first-page to /en/second-page, for fr and zh locales redirect is correct.

Also found unnecessary redirect for config
{ source: '/first-page', destination: '/', permanent: true }

and in this case we have three redirects instead of two: /first-page -> /en/ -> /en, /fr/first-page -> /fr/ -> /fr

[dmitrykozyrenko]

Created two separate issues #19405 #19403

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.