Bug with next-i18next and deployment on Vercel

[serGlazkov]

Provide environment information

"next": "12.2.5", // Also tested on 12.2.6-canary.7 and 12.1.6
"next-i18next": "12.0.0", // Also tested on 10.5.0
"react": "18.2.0", // Also tested on 17.0.2
"react-dom": "18.2.0" // Also tested on 17.0.2

How are you deploying your application?

Vercel

Bug Description

Context

We encountered a bug around next-i18next that resulted in serverless crashes for catch-all routes. We noticed this bug for the first time Monday around 14:00 CET and think it is potentially related with a change in the serverless runtime/filestructure as older deployments that used to work stoped working when redeploying.

Some other people also seemed to have encountered the same bug. See also here:

• This discod thread
• This next-i18next bug report
• Stackoverflow same problem

What we tried

So we upgraded our versions of next and next-i18next (like some of the other people did).
With the most recent next.js and next-i18next versions translations seem to work only in very specific cases.

We created a minimal replicable deployment (Repo) where we prebuild two pages via putting them in getStaticPaths:

• https://ed-i18n-bug.vercel.app/en/test/prebuild
• https://ed-i18n-bug.vercel.app/de/test/prebuild

Both pages do not use translations when opening them directly.

However, when first navigating to the index.js and then clicking on of the links the two pages use proper translation.

Note: The translations will break upon refresh.

Setup Description

• catch all route in pages folder
• page set to static site generation
• default locale is set
• incremental static regeneration is on

Expected Behavior

working Translations

Links to Reproduce

Example repo here: https://github.com/everdropde/ed-i18n-bug
Example Vercel Deployment: https://ed-i18n-bug.vercel.app/de

Steps To Reproduce

1. Clone the Repo and deploy it to Vercel
2. Click any link on page

[adrai]

You may open/reference this issue in the Vercel / Next.js repo. -> vercel/next.js#40130
Sound like to be a Vercel issue.

[breiko83]

Hello - having the same issues here. Posted on Vercel discussion: vercel/next.js#40099

[FBosler]

Could this be the reason? vercel/nft#304

[swarnava]

Setting VERCEL_CLI_VERSION=vercel@28.1.4 should fix the issue while we working on a permanent fix for this.

[swarnava]

Hi, could you confirm if you have outputFileTracing disabled ? If you have it enabled and using latest version of Next.js then this should work with latest CLI version

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.