New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link
pointing to built pages no longer works on canary
#35135
Comments
Link
pointing to /
no longer works with 12.1.1-canary.7
Link
pointing to certain pages no longer works with 12.1.1-canary.7
Link
pointing to certain pages no longer works with 12.1.1-canary.7
Link
pointing to built pages no longer works on canary
After further investigation, it seems that the problem isn't I've updated the bug explanation and the steps for reproducing it. |
### Bugfix Made some changes for the data register buffer flushing in #34631 and #34475 that tried to delete the buffer or flush them only once. But turns out it will break the navigation between RSC pages. ### Enhancements Simplify the inline response writer and inline response data for the initial render. Since they're only for the initial render, navigations will leverage the serialized data fetched from router and construct the react tree. ## Bug Fixes #35135 - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md`
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. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
Chrome 98.0.4758.109
How are you deploying your application? (if relevant)
Vercel
Describe the Bug
With version
12.1.1-canary.7
ofnext
, aLink
pointing to a route on which you've initially entered the application longer does anything when clicked.It's possible to reach any route via
Link
, just not the page on which you've loaded the app initially.The URL in the address bar of the browser is set to the correct URL, but no page transition occurs. I also checked the console, but there aren't any errors. Same for the terminal.
Note that I'm using React Server Components on the Edge Runtime.
Expected Behavior
I'd expect a
Link
that points to a page on which I've loaded the app initially to still work.To Reproduce
Link
withhref
set to any other routerm -rf .next
(just to be sure)href
for theLink
Link
Link
href
, but no page transition occurs.The text was updated successfully, but these errors were encountered: