Загрузка видео...

Не удалось загрузить видео

На главную

Internationalization (i18n) in Next.js 13

201,740 просмотров • 2 лет назад •via X (Twitter)

Комментарии: 9

Фото профиля Frank Spin
Frank Spin2 лет назад

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
ibrahim uzun2 лет назад

don't forget this

Фото профиля JM
JM2 лет назад

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

Фото профиля Tomas Jansson
Tomas Jansson2 лет назад

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 🇬🇧
Daniel Cranney 🇬🇧2 лет назад

These animations are siiiiilk 😍

Фото профиля KODMAN
KODMAN2 лет назад

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
MrMax2 лет назад

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

Фото профиля LukeberryPi
LukeberryPi2 лет назад

olha que foda @frontfabii @ducaswtf

Фото профиля Bart Proost
Bart Proost2 лет назад

Keep m coming ❤️

Похожие видео