Next.js multi zones with i18n and shared components #28683
Unanswered
amosbastian
asked this question in
Help
Replies: 1 comment
-
Did you solve this ? (: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using Next.js' multi zone feature with a blog and web app so I can develop and deploy both apps independently. It was easy to set up by following the with zones example and I have set up a blog app at port
4200
and a web app at port3000
, which is working fine. Unfortunately I am encountering some problems that aren't described anywhere in Next.js' documentation (as far as I can tell).First of all, I am also using internationalised routing which is working fine, however when going to my blog app it appends the locale to the end of the URL. Imagine I am on
localhost:3000/en
and navigate to the blog app, then it will showlocalhost:4200/blog/en
instead oflocalhost:4200/en/blog
. Is there any way around this (e.g. by using rewrites)?Secondly, I am working in a monorepo and have shared components between both apps, such as the header and footer, which obviously includes navigation. When I am on the blog and want to navigate to e.g. the
/about
page, then it will obviously navigate tolocalhost:4200/blog/about
instead oflocalhost:3000/about
. One solution is to check the base path in the navigation component and then prepend e.g.localhost:3000
to thehref
if the base path equalsblog
, but that refreshes the entire app and does not result in smooth navigation, so it's not really ideal. Is there anything else can I do about this?It seems others also have the same problem, and I can't find anything about this in Next.js' documentation, so any help would be appreciated 😁
Beta Was this translation helpful? Give feedback.
All reactions