Blitz: [Feature Request]: Add i18n

[Fghurayri]

What do you want and why?

i18n is immensely needed in any web __framework__.

Possible implementation(s)

The Nextjs community are yet to agree on the best possible way to implement i18n while keeping SSR / SSG / Serverless working as expected.

Can this be solved by Blitz?

Additional context

https://github.com/zeit/next.js/discussions/10651

[flybayer]

I've never implemented i18n myself, but I agree Blitz should solve this.

So I'd love to hear proposals or ideas on how we should do this!!

[waptik]

So after going through all possible solutions/examples, with-i18n-rosetta looks like the best possible solution at the moment (demo) . No difficult setup nor extra build steps.
Besides, you can also use your locales as packages and easily import them in your projects like how Uppy does it.

[flybayer]

Awesome, thank you @waptik.

So it appears very likely that the Next.js team is working on an official i18n solution (source and source). I think we should wait and see that before doing something ourselves.

Only bummer is they haven't given a timeline.

[waptik]

@flybayer 😱 wow, that's great news 😋. I think an official solution is the best way to go, especially if it's coming from the authors.
So it's worth waiting 😊
Thanks for sharing the good news

[wescopeland]

A quick update on this: next-i18next now supports serverless i18n from their beta branch. The implementation relies on path rewrites, which are currently behind an experimental flag but will be GA on the next stable release.

[flybayer]

The Next.js RFC on i18n Routing has just been posted!

[jan-wilhelm]

any news on this, now that NextJS 10 is used in Blitz and includes official support for i18n routing?

[flybayer]

@jan-wilhelm no news! Now that that's released, it's up to y'all to decide if there's more stuff that we should add on top of that in blitz.