Skip to content
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

Closed
ghost opened this issue Nov 29, 2018 · 8 comments
Closed

Sometimes <Link>'s don't work in dev #5772

ghost opened this issue Nov 29, 2018 · 8 comments

Comments

@ghost
Copy link

ghost commented Nov 29, 2018

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

  • OS: macOS
  • Browser: safari
  • Version of Next.js: "next": "^7.0.2",
@rodrigooler
Copy link

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.

@swolidity
Copy link

I think this might be a duplicate of #5598

@Enalmada
Copy link
Contributor

You could try this workaround and that would help confirm if this is a duplicate of that:
vercel/next-plugins#282 (comment)

@malimccalla
Copy link

malimccalla commented Nov 30, 2018

If this is the same issue as #5598 see this workaround #5598 (comment)

@rodrigooler
Copy link

I was able to solve my problem, it was basically a Provider that was giving problem to render the page.

@swolidity
Copy link

@rodrigooler like a HOC component like ApolloProvider?

@rodrigooler
Copy link

@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.

@timneutkens
Copy link
Member

Duplicate of #5598 indeed

@lock lock bot locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants