What part of the code deals with making requests to the http server when Link is clicked for production?

[R4R3D1FF]

Summary

I've realised that in production, Link components is making multiple requests to the server for parallel routes, when it should be making just one. Can someone tell me which part of the code deals with Link?

I thought it should be the prefetch function in link.tsx, but I tried logging it and didnt see any output, neither in the browser nor in VScode.

Additional information

No response

Example

No response

[icyJoseph]

Mm I see you found that parallel routes issue too 🤔

Maybe a good place to start debugging is the navigation reducer?

• next.js/packages/next/src/client/components/router-reducer/reducers/navigate-reducer.ts

  Line 171 in ea08bf2

  export function navigateReducer(

There's a quite a bit more going on too - and I wonder if the clientSegmentsCache has any influence on this behavior too - I haven't had time to test - https://nextjs.org/blog/next-15-4#preview-upcoming-features

[R4R3D1FF]

I couldnt really find anything there

Its only an issue in production
the requestListener that the http server is started on is being called as many times as parallel routes, in addition to the layout
I havent yet tested the clientSegmentsCache but if it is the cause then this must be a regression, right? It could be verified by testing against an old version

[icyJoseph]

I'd expect clientSegmentCache to fix this rather, it is not activated by default, so it wouldn't be

I haven't debugged this issue yet though