search

vercel / next.js

The React Framework
https://nextjs.org
MIT License
122.66k stars 26.25k forks source link

PPR + Route Interception leads to corrupted params value #64265

Open olliejm opened 2 months ago

olliejm commented 2 months ago

Link to the code that reproduces this issue

https://github.com/olliejm/angry-hypatia-3plyfm

To Reproduce

  1. Run yarn dev or yarn build && yarn start, inspect port 3000, click the link to trigger the intercepting route, observe parameter values A and B
  2. Deploy the repository to Vercel, click the same link, observe that B is now B.prefetch. See deployed version to verify

Current vs. Expected behavior

Currently the parameter value is becoming corrupted when deployed to Vercel. It only happens when PPR is enabled.

Provide environment information

Only applies in Vercel

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

App Router, Routing (next/router, next/navigation, next/link)

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

Vercel (Deployed)

Additional context

No response

Diabl0570 commented 2 months ago

I have this issue as well, but I am not using PPR nor Route Interception (for that route anyway, I do on a other page)