Strategy for fully sever-side translations with App router. #1013
Replies: 1 comment 1 reply
-
Thanks for sharing your thoughts @markoleavy! Keeping i18n purely on the server side definitely has it's advantages, but I think I wouldn't push it too dogmatically (depending on your app). In regard to avoiding prop drilling, there's an example in the Passing translations to Client Components docs in the expandable section "How can I implement a form?". Sometimes the way how you structure your components (by accepting That being said, there's absolutely a necessity for handling i18n in Client Components in Next.js apps. I'd like make this more natural to handle in the future without performance drawbacks (see e.g. #962 and #1). In any case, your approach will definitely continue to work! |
Beta Was this translation helpful? Give feedback.
-
Hi everybody,
I've just published an article on Medium, that shows a strategy to implement next-intl with app router and server-side translations, simplifying the typing and field translation process.
I would love to know what you think about it, and if it could be the base for a new feature!
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions