#Remix With localization

1 messages · Page 1 of 1 (latest)

lethal peak
#

Hello all, I have a question. I am trying to do an app with localization, on the url, and based on that I can fetch data from a backend with custom locale, now I've tried this approach however, I am not a big fan of having to nest everything under the $locale folder, following this example https://github.com/AnandChowdhary/remix-starter just wondering if this would be the best approach? I've also tried this and followed this, but couldn't figure out a way to get the locale from the URL https://github.com/sergiodxa/remix-i18next, any ideas or example that I can try out?

GitHub

💿 Starter for @remix-run with localized routing and i18n - GitHub - AnandChowdhary/remix-starter: 💿 Starter for @remix-run with localized routing and i18n

barren lion
#

For now, yes. I cannot move my existing app to remix because of that.

However, you can localise based on either subdomain or query param. something like mydomain.com/user?lang=en

#

And defaults can be used from browser language.

lethal peak
#

ohh, that's a shame. I wanted to move my NextApp to Remix, but I really like the way they handle localization, is much straight forward

barren lion
#

@lethal peak not anymore with app directory in nextjs yet 🙂

I believe remix will have a solution faster than next which is inspiring from remix.

lethal peak
#

I haven’t tried the new next js, but not sure it would change the way it works right now

#

Nvm just saw that in fact is the same way, you would have to nest everything inside [locale] folder 🤔

barren lion
lethal peak
#

Let’s see which one comes with a better solution, not a big fan of the nesting as of now. So I’m still using next12 for it, but wanted to go to remix

barren lion