Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Back button for rewritten page broken in last version
See original GitHub issueWhat version of Next.js are you using?
10.2.3
What version of Node.js are you using?
14
What browser are you using?
Chrome
What operating system are you using?
macOS
How are you deploying your application?
none
Describe the Bug
Pressing the back-button to a rewritten page causes this bug for us in the latest version:
Seems like shouldResolveHref, which was added in https://github.com/vercel/next.js/pull/25112 is now false and the router is not able to resolve the href anymore.
Expected Behavior
Back button to work.
To Reproduce
Have a page that is served through a rewrite, go to another page through a next/link transition (only reproducible on the second transition when the page has not been built yet and you’re testing it locally), go back to the previous page with the browser back button will throw this error.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ijjk I just tested this with my integration test and it still seems broken. (https://github.com/vercel/next.js/pull/25666#issuecomment-852393471) will see if I can fix it.
This is happening to me and we don’t use
getServerSideProps. We do have dynamic routes and use params in the rewrite, but only one.