-
Notifications
You must be signed in to change notification settings - Fork 26.3k
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
Sometimes <Link>'s don't work in dev #5772
Comments
I have these same problems with the Link and Router, unfortunately I had to force on hand with window.location.href, as I have not figured out how to solve. |
I think this might be a duplicate of #5598 |
You could try this workaround and that would help confirm if this is a duplicate of that: |
If this is the same issue as #5598 see this workaround #5598 (comment) |
I was able to solve my problem, it was basically a Provider that was giving problem to render the page. |
@rodrigooler like a HOC component like ApolloProvider? |
@iamandyk yes, in my case I am using a redux alternative that is the reworm and it has a provider that I put in the _app ... In this both the and the Router.push have stopped working. When removing returned to work normally, hence my solution was to instantiate the provider inside a HOC and only call when it will use. The route system has returned to normal. |
Duplicate of #5598 indeed |
Bug report
Describe the bug
Sometimes when I have links they don't want to load in my dev environment. However when it's on the cloud it works fine. I'm not sure why.
To Reproduce
Don't really know what steps I can do. Sometime's it works, sometime's it doesn't. If I refresh the page in a new tab, it will work as expected.
<Link href="/config/link"><a>Text Here</a></Link>
Expected behavior
For it to go to it's respected link.
System information
"next": "^7.0.2",
The text was updated successfully, but these errors were encountered: