On one page of my app, all functions or components from next/navigation are not working. I can ctrl+click on a Link component and it'll open the link in a new tab, but I can't click normally to open in the current tab.
This does not happen on all pages.
Regular anchor tags still work normally
#next/navigation fails on one page
sharp whale
verbal doveBOT
Hi @sharp whale. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the information provided in the extracts, it seems like you're experiencing a known issue with Next.js where navigation fails on certain pages. This issue has been reported in various forms on the Next.js GitHub repository.
For instance, in issue #49812 (https://github.com/vercel/next.js/issues/49812), users reported that navigating away from a not-found page via next/link doesn't work. A similar issue was reported in issue #48367 (https://github.com/vercel/next.js/issues/48367) where next/link navigation was broken after adding a not-found page.
In issue #48836 (https://github.com/vercel/next.js/issues/48836), a user reported that navigation for a global not-found page in the App Router didn't work. When navigating to such a page, or from it using next/link, the address changed in the browser, but the browser kept showing the same page.
In issue #49255 (https://github.com/vercel/next.js/issues/49255), a user reported that the next/link component in the app directory was not working properly in terms of scroll behavior.
In issue #53624 (https://github.com/vercel/next.js/issues/53624), a user reported that next/link was very slow and sometimes didn't work.
In issue #45663 (https://github.com/vercel/next.js/issues/45663), a user reported that a component was not showing when navigating between pages.
In issue #46605 (https://github.com/vercel/next.js/issues/46605), a user reported that the className prop did not match when using Next.js 13 with styled-components, without the app folder.
In issue #44568 (https://github.com/vercel/next.js/issues/44568), a user reported that the Next.js Link component relative path navigation went to the wrong path.