-
-
Notifications
You must be signed in to change notification settings - Fork 799
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Add i18n #279
Comments
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!! |
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. |
@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. |
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. |
The Next.js RFC on i18n Routing has just been posted! |
any news on this, now that NextJS 10 is used in Blitz and includes official support for i18n routing? |
@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. |
After working with "raw" NextJS i18n for a while, I've found |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
vercel/next.js#10651
The text was updated successfully, but these errors were encountered: