-
Notifications
You must be signed in to change notification settings - Fork 27.1k
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 component broken on error and not-found pages #48073
Comments
Same issue for me as well , Link component in global not-found.js is not working . Tried with router.push() still didnt work |
I also want to confirm that something is broken with links on In addition I also want to point that when |
Related to #47862 |
Seeing exactly the same thing as described here: #48073 (comment) Links in other parts of the layout (header etc) also only change the url but nothing re-renders and we're stuck on the not-found page. Running "next": "13.3.0" |
Duplicate of #47862 |
|
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
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.1.0: Sun Oct 9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 Binaries: Node: 16.17.0 npm: 8.15.0 Yarn: 1.22.19 pnpm: 7.13.1 Relevant packages: next: 13.3.0 eslint-config-next: 13.3.0 react: 18.2.0 react-dom: 18.2.0
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true)
Link to the code that reproduces this issue
https://stackblitz.com/edit/vercel-next-js-fzljky?file=app%2Fnot-found.tsx
To Reproduce
Go to any not-found page. Happens also on regular error pages
Click the link to go to homepage
Describe the Bug
Navigation doesn't work
Expected Behavior
I go to the homepage
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: