-
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
gatsby develop: page query hanging #26530
Comments
I'm also having this issue after updating Gatsby.
npm 6.14.8 Temporarily working around this issue by rolling back to Gatsby version 2.23.1 Steps to reproduce
|
@sidharthachatterjee @freiksenet or @vladar, do you have any ideas? |
@swkeever Can you please check what is the latest version where it works for you? Is it 2.23.1 or maybe it works on later versions as well? Basically we need to find a first versions that breaks. |
A quick investigation shows that it is probably somehow related to MDX (not 100% sure yet though) |
If I remove There is a bug report in |
Got it. Thank you for looking into this. |
It could be actually caused by core changes. The referenced issue mentions that the problem was introduced in 2.24.9. If so, then this PR can be a culprit: #25479 I am going to re-open this issue until we confirm it's a plugin, not a core issue. |
What I've discovered so far:
But since this I am not sure yet what is the right course of action to fix this. |
Also, I guess the same issue will occur in any plugin calling |
This PR was supposed to fix a similar issue: #26138 so maybe just need some follow up |
To recap: the problem is that any node mutations (createNode, deleteNode, etc) are now deferred until develop machine reaches the I don't have enough context on our state charts yet to fix this correctly. The only idea I have so far is to debounce the |
I'm closing this because it should be fixed in the latest version. I have tested it with @swkeever 's site and confirmed that it now works. If anybody is still having the problem with the latest verison of gatsby, please open a new ticket that includes the output from |
Tried
gatsby clean
, Updated gatsby from 2.24.37 to .2.24.47Node version: v10.16.3 (npm v6.9.0)
OS: MacSierra
The text was updated successfully, but these errors were encountered: