Getting `Loading (StaticQuery)` with version 2.24.11 (production only)
See original GitHub issueDescription
When using version 2.24.11
and StaticQuery
we get Loading (StaticQuery)
(production only) (code).
When using 2.23.22-static-query-template.8
the problem is solved.
Steps to reproduce
Unfortunately this issue only happens when we deploy to production, so I’m not sure how I can help you to reproduce it without breaking our docs 😕
Expected result
StaticQuery should return a result.
Actual result
Loading (StaticQuery)
is shown.
Environment
System: OS: macOS Mojave 10.14.6 CPU: (12) x64 Intel® Core™ i7-8850H CPU @ 2.60GHz Shell: 5.3 - /bin/zsh Binaries: Node: 11.13.0 - ~/.nvm/versions/node/v11.13.0/bin/node Yarn: 1.19.1 - /usr/local/bin/yarn npm: 6.13.4 - ~/.nvm/versions/node/v11.13.0/bin/npm Languages: Python: 2.7.10 - /usr/bin/python Browsers: Safari: 12.1.2 npmPackages: gatsby: ^2.2.2 => 2.24.11 gatsby-image: ^2.0.34 => 2.4.13 gatsby-plugin-manifest: ^2.0.24 => 2.4.21 gatsby-plugin-offline: ^2.0.25 => 2.2.10 gatsby-plugin-react-helmet: ^3.0.10 => 3.3.10 gatsby-plugin-sass: ^2.0.11 => 2.3.12 gatsby-plugin-sharp: ^2.0.29 => 2.6.22 gatsby-source-filesystem: ^2.0.27 => 2.3.23 gatsby-transformer-react-docgen: ^5.0.0 => 5.2.11 gatsby-transformer-remark: ^2.8.3 => 2.8.27 gatsby-transformer-sharp: ^2.1.17 => 2.5.11 npmGlobalPackages: gatsby-cli: 2.12.66
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:41 (12 by maintainers)
Top GitHub Comments
With only changing the
gatsby@2.24.13
version I still got the error.Sorry everyone — I had expected/received reversed as several of you pointed out. Published a new version of check-gatsby-caching with it fixed.