-
Notifications
You must be signed in to change notification settings - Fork 10.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
Uncaught TypeError: Cannot read property 'call' of undefined #2804
Comments
Seems like there's a JS error in your code? This doesn't happen with vanilla Gatsby. |
It seemed to be happening in Gatsby generated code. Its not happening anymore so I'll close this issue and reopen if I see it again. |
@pzatrick I just started seeing the same issue. Has it come back by chance? It happens (seemingly) randomly when clicking on When I get the error, this is the order of errors: |
When I look up the missing module id, it seems to trace back to lodash. 🤔 Edit: I'll continue digging in and post here if I find anything. |
This issue may be a duplicate of #1043. |
@danoc did you find any fix? |
@whispers16 – I think it eventually started working but I didn't know what the fix was. My best guess is that it was related to the weird way that I was using the Link package. I was building many different Gatsby sites (different repos) then combining them by copying over the dist folders. |
I think (most commonly) it is a file caching issue, I've run into it a few times for a brief stint (see #1043 (comment)) |
Gatsby CLI version 1.1.19
Node version 8.6.0
macOS 10.12.6
gatsby-config.js
package.json
When I click a link made using the
Link
component fromgatsby-link
that leads back to my site index I get this error and the index page doesn't load. However if you click the link again it works.For now I've created this workaround which devolves
pushState
to a regular location change with full reload:The text was updated successfully, but these errors were encountered: