Next.js Internationalized Routing not working

[ErikWittern]

First of all, this effort is fantastic, thank you for pursuing it.

One of the Next.js features that require a Next.js server is Internationalized Routing. In a demo project I created, configuring Next.js internationalization for sub-path routing (cf. https://nextjs.org/docs/advanced-features/i18n-routing#sub-path-routing) works exactly as expected when running the page locally using firebase serve. However, the deployed version only always uses the defined defaultLocale.

Notably, the other language version of the page is available at the sub path (in my case, /de) after deployment - but server-side forwarding does not occurr as expected. Possibly the Accept-Language header is not passed to the SSR Cloud Function correctly in the deployed version?

[jamesdaniels]

Internationalization is on our short list! Thanks for giving it a spin.

[alexjball]

@jamesdaniels Are you planning on supporting i18n routes via Firebase's i18n rewrite feature, or as part of the existing deployment scheme (static files + SSR function)?

[andrashee]

Hi @jamesdaniels. What is the status of this? Having the i18n feature working in firebase would be a gamer changer!

[jamesdaniels]

The plan is to leverage the existing Firebase i18n rewrites as much as possible here, if there's a delta in capabilities we will spin up a Cloud Function. We're working on making rewrites/redirects/headers more robust now, this work will naturally follow that.

No timeline to share but it's in the next planned set of updates.

[ssandino]

@jamesdaniels any update on i18n compatibility? I saw Firebase saw some nice updates ...