Default Fallback Page Inside Parallel Routes Causes Infinite Reload in next dev

[tj-noor]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:23 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6020
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: N/A
  pnpm: 8.6.5
Relevant Packages:
  next: 13.4.9-canary.2
  eslint-config-next: 13.4.8
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.6
Next.js Config:
  output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

Link to the code that reproduces this issue or a replay of the bug

https://github.com/tnoor-co/next-infinite-parallel-refresh

To Reproduce

1. install packages - pnpm install
2. run next dev - pnpm dev
3. navigate to http://localhost:3000/home/nested directly to experience the infinite refresh right away.
   • Timestamp will update on each render.
   • Server logs from the middleware will populate on each reload
4. alternatively, navigate to http://localhost:3000/home/ and then click on the hard navigation and/or the next link for http://localhost:3000/home/nested
   • hard navigation link refreshes infinitely
   • next link behaves as expected and does not refresh infinitely

Reproduced with next@13.4.9-canary.2

app/
  - layout.tsx
  - page.tsx
  - @parallelA/
    - default.tsx
    - page.tsx
  - @parallelB/
    - page.tsx
    - nested/
      - page.tsx   <------- infinite reload here

Describe the Bug

During local development in next dev, a nested page inside of a parallel route without a corresponding matched route inside another parallel route causes an infinite reload, despite the required default file meant to render as a fallback.

ref:
#52061
#51951 (comment)

Expected Behavior

The page should only reload if changes were made to it or if the page returns a 404.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[tj-noor]

As a temporary workaround, I patched the following file in my project to avoid the fetch call IF "pong" event had invalid set to true ->

next.js/packages/next/src/client/components/react-dev-overlay/hot-reloader-client.tsx

Line 421 in 21392cb

fetch(window.location.href, {

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.