You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
exportdefault()=>(<div><Header/><p>This is our homepage</p><div><Linkprefetchhref='/blog'><a>Blog</a></Link></div><div><Linkprefetchhref='/about'><a>About us</a></Link></div><imgwidth={200}src={asset('/nextjs.png')}/></div>)
I am getting the Page does not exists message in the console, so prefetch is not working.
This is because app A does not know about app B, cause they are reached with a proxy.
How to implement prefetch in this case?
Thanks.
The text was updated successfully, but these errors were encountered:
Prefetching doesn't work with zones. Since moving from zone-to-zone is a hard page refresh for various reasons, for example multiple zones could run multiple versions of Next.js, React and other dependencies.
@timneutkens Despite you are right: prefetch doesn't work with zones, I am very convinced that splitting your app into multiple micro-services is a good strategy for mantaining/deploying/scaling purposes. So, how to get best of both?
Going to basics, there is actually a really simple workaround I found talking in Slack channel, that I want to share here for posterity.
You can simple include, in your Head component, this:
Hello, I have implemented this pattern on my deploys:
https://github.com/zeit/next.js/tree/canary/examples/with-zones
With the links with the
prefetch
attribute, like:I am getting the Page does not exists message in the console, so prefetch is not working.
This is because app A does not know about app B, cause they are reached with a proxy.
How to implement prefetch in this case?
Thanks.
The text was updated successfully, but these errors were encountered: