-
Notifications
You must be signed in to change notification settings - Fork 75
StaticQuery is not working #232
Comments
The problem is caused by a change in the gatsby's Change in the gatsbyjs: |
Pull request has been created for the fix in the |
Hi @gforro can you make the PR here and we'll merge it into an upstream package? |
If anyone is having the same issue with staticquery, or an issue with a broken dependency in the gatsby-source-prismic-graphql, I fixed mine by switching from this branch to the @prismicio branch mentioned by @MarcMcIntosh that has more fixes applied. For NPM newbies like me that need more specific instructions: The easiest way I found to seamlessly switch to the prismic fork was to remove the old package, and then install the prismic version as an alias Can also be done by adding this to your package.json dependencies |
The static queries stop to work, when the gatsby-source-prismic-graphql plugin is configured to be used. The problem is that the query is stucked for some reasons and the
Loading (StaticQuery)
message is shown in a page, where a component with a simple static query is used. It is enough to use thestatic-query
example from this repositories to reproduce the problem. Steps to reproduce the problem:gatsby-source-graphql-universal
- Error: Cannot find module './third-party/gatsby-node):Add to the
scripts
part:gatsby-node.js
to fix the issue with the cache (problem when gatsby cache is cleaned):<Layout>
part in the index.js page.Now You will get the problem!
The text was updated successfully, but these errors were encountered: