next-i18n support

[paales]

I'm looking to implement https://github.com/isaachinman/next-i18next as well. Not sure if this is something in the scope of this package, but (optional) support would be nice.

I really like where this project is going and is already offering a lot of value as is, and we are investigating how we can use this in our frontends. Almost all our frontends we are building will require some form of i18n.

It would be nice if if we're able to achieve something like:

• Service orientated i18n, create namespaces based on the services that are available.
• Support URL-based language routing /en, /jp, etc.
• ...

[tonyfromundefined]

Thank you for your attention to my next-starter project. This repo contains a lot of know-how gained from my production distribution. I'm so glad you helped with your project.

I will add the i18n feature as soon as you suggest. However, due to the lack of experience with i18n at the Production level, I can not say for sure that the service availability by locale feature will be implemented soon.

But, I will continue to think about the issues as a good suggestion. If your team solves this problem, I will gladly accept it if you give us a Pull-Request.

[paales]

I've started working on the i18n stuff, but I am going to run into an issue with serverless deployments (which we haven't even decided if it is necessary).

https://github.com/isaachinman/next-i18next/issues/274