you can usePathname() (from next.js) to get the full path instead

therefore no need useContext nor any creation of additional context

thanks a lot! I will try that

useContext won't prevent a server prerender though

a client component can be prerendered on the server and will be then hydrated on the client

here usePathname is indeed more direct though it basically does the same already

but you have to make the component a client component (most often it's fine because deeply nested component are usually client components)

https://stackoverflow.com/questions/66106408/retrieve-data-server-side-and-save-in-context-with-next-js/75533592#75533592 for more details around context

Thanks for the references! I will read a bit more into it so that I understand it

Thanks for the insightful articles! I really like the first one about advanced nextjs server context. @Eric Burel
It sounds nice to use Reacts cache function to cache the translations per locale and then get them in the components on the server. But then I get the problem that I don't know how to get the path name on the server and only can get it with usePathname on the client. Maybe that makes sense because a component could be rendered on multiple paths..

I double checked my own code an I must admit I tend to props drill in this case

but the server-only-context trick (the github link from manvalls) normally allow to set the route params in the cache and get it from nested components

I am pretty sure Next will include solutions to do that in the future, there has been work around contexts internally

and accessing the URL is a subject that leads to heated discussion on GitHub

Next often takes time to solve this but when they do they provide sleek solutions, in the meantime "cache" does the job

again you don't usually have a super deep RSC tree in most apps yet

Thanks! Yea there is a lot of development on it I guess. I used a set-up loosely based on this blog article now for i18n: https://carlogino.com/blog/nextjs13-i18n
I'm struggling with using the next locale settings though. It switched from the /pages directory to the /app directory and on the pages directory everything was fine but on the app directory I get 404's for different languages. NextJs documentation on i18n seems unchanged and doesn't mention differences between these two approaches. I think for now I will not use the i18n configuration parameter and just set i18n based on path parameter.

in the app router you normally implement i18n more "directly" by using the framework

rather than relying on the built-in config

Check how we implement i18n here starting from the middleware: https://github.com/Devographics/Monorepo/tree/main/surveyform

Thanks, that clears things up 🙂 really clear code