vercel/next.js

[bug]: parallel/intercepting routes requires server reboot to work

juliusmarminge opened this issue · 0 comments

Link to the code that reproduces this issue

https://github.com/juliusmarminge/next-intercepting-routes

To Reproduce

  1. Start the dev server
  2. Navigate to the parallel segment (e.g http://localhost:3000/dashboard/1/1)
  3. Click on a card, it opens in a modal
  4. Now suppose we change the URL structure, so rename audit to auditt (in both places) and update the link to point to the new pathname. Refresh the page and click the card again, it opens in the full-page view
  5. Restart the dev server, refresh the page again and now it opens in the modal view

Demo:

CleanShot.2024-12-11.at.17.36.52.mp4

Current vs. Expected behavior

It requires a server reboot when it shouldn't

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Nov 15 19:28:48 PST 2024; root:xnu-11215.61.3~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.1-canary.0 // Latest available version is detected (15.1.1-canary.0).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.5.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

Changing the path like this might not be very realistic, but I wasted a lot of time to understand why my parallel routes wasn't working when adding them yesterday, trying to understand the necessary folder structure. Then I tihnk i went and added a dep and when i started the server back up it was working all of a sudden... It wasn't until i was fighting another issue (#73801) and ran into it again when trying other stuff that I understood that this was the issue