We've been working with i18n (internationalization) for a few months, and we couldn't find any easy way of knowing what's the user's language that works both on the browser and on the server.
There are tons of libs out there, but none that are working universally. So, we decided to outsource our proprietary implementation and release it under MIT license.
Also, because we're fans of the Next.js framework, we've made an integration example with a demo available there:
https://universal-language-detector.now.sh/
https://github.com/UnlyEd/universal-language-detector
Did you get stuck too with a similar issue when implementing i18n? How did you sort it out? Does this lib help? Let us know! :)
Top comments (1)
Our universal language detector is now featured in github.com/UnlyEd/next-right-now, check it out!