Catch all route is unexpectedly activated when combined with parallel intercepting route in next dev --turbo

[typeofweb]

Link to the code that reproduces this issue

https://github.com/typeofweb/repro-nextjs-intercepting-catchall

To Reproduce

1. Clone the repository
2. Run pnpm install
3. Run pnpm dev
   1. Open http://localhost:3000
   2. Click on the link "Open cart"
   3. Observe correct behavior where the catch all route is not used and the intercepting parallel route is used.
4. Run pnpm dev --turbo
   1. Open http://localhost:3000
   2. Click on the link "Open cart"
   3. Observe incorrect behavior where the catch all route is used together with the intercepting parallel route.

Current vs. Expected behavior

Expected (the catch all route is not activated):

Unexpected (the catch all route is activated):

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Mon Aug 12 21:29:00 PDT 2024; root:xnu-11215.1.10~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.16.0
  npm: 10.8.1
  Yarn: N/A
  pnpm: 9.8.0
Relevant Packages:
  next: 15.0.0-canary.130 // Latest available version is detected (15.0.0-canary.130).
  eslint-config-next: N/A
  react: 19.0.0-rc-b57d2823-20240822
  react-dom: 19.0.0-rc-b57d2823-20240822
  typescript: 5.5.4
Next.js Config:
  output: N/A

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

Parallel & Intercepting Routes, Turbopack

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

next dev (local)

Additional context

No response

[github-actions]

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