intercepting routes not rendering under nested route about next.js HOT 3 CLOSED

Hi @V01D-NULL

I believe this is because your parallel slot is defined at the foo level, not at the root level. In this case, the parallel route would be passed as a prop to app/foo/layout.tsx (if it existed), rather than app/layout.tsx.

If you create a app/foo/layout.tsx file that looks like this, it should work as you expect!

export default function Layout({ children, modal }) {
  return (
    <>
      {children}
      {modal}
    </>
  );
}

from next.js.

@ztanner

You're right that did help, our production env has this too I must have missed it while creating this poc.
The issue I'm seeing on production is intermittent, sometimes the intercepted renders a modal, sometimes it doesn't. Using just a Link component for that..

Does this sound familiar at all?
This was my best shot at trying to replicate the behavior I saw, due to the volatile nature of the bug I'm seeing I was unable to create a standalone reproduction

from next.js.

@V01D-NULL I'm afraid it's hard to say without seeing the source. You might be able to debug the behavior a bit better if you add a catch-all slot to your interception route (ie, @slot/[...catchAll]/page.tsx) as well as a root page (ie @slot/page.tsx) and have them render some debug code. This might help diagnose if your interception route is being matched to the wrong page component.

from next.js.