Loading video...

Video Failed to Load

Go Home

Internationalization (i18n) in Next.js 13

201,740 views • 2 years ago •via X (Twitter)

9 Comments

Frank Spin's profile picture
Frank Spin2 years ago

Good introduction. But in the real world you also need translated slugs in the corresponding language. So you need redirects and rewrites. Also important to add the right canonical links.

ibrahim uzun's profile picture
ibrahim uzun2 years ago

don't forget this

JM's profile picture
JM2 years ago

It would be also nice to have /en/hello and /es/hola but quite nice 👌🏽

Tomas Jansson's profile picture
Tomas Jansson2 years ago

Nice. We have a similar solution implemented. Not exactly the same since all countries have different host name. One thing I would do for the default one is rewrite instead of redirect, but I guess that is a matter of use case and requirement.

Daniel Cranney 🇬🇧's profile picture
Daniel Cranney 🇬🇧2 years ago

These animations are siiiiilk 😍

KODMAN's profile picture
KODMAN2 years ago

It works perfectly for server components, but then you have a client component. It's really hard to maintain. Next-translate package handles both.

MrMax's profile picture
MrMax2 years ago

what is the hello page is for /en but for /es you call it ola, how would this work ?

LukeberryPi's profile picture
LukeberryPi2 years ago

olha que foda @frontfabii @ducaswtf

Bart Proost's profile picture
Bart Proost2 years ago

Keep m coming ❤️

Related Videos