question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"gatsby-source-graphql" threw an error while running the sourceNodes lifecycle:

See original GitHub issue

Description

On build, the following error is thrown "gatsby-source-graphql" threw an error while running the sourceNodes lifecycle:; TypeError: createResolveType is not a function. I found this issue in my Continuos delivery process and was able to replicate locally after reinstalling node modules to get the latest version of gatsby-source-graphql, that was published to npm about 1 hour ago, 2.1.26. Before, I was running “gatsby-source-graphql”: “^2.0.18”

Steps to reproduce

Install latest package version and run the build command.

Expected result

run build without no issues

Actual result

the build process is stopped

Environment

System: OS: macOS 10.14.6 CPU: (16) x64 Intel® Core™ i9-9880H CPU @ 2.30GHz Shell: 5.3 - /bin/zsh Binaries: Node: 8.16.0 - ~/.nvm/versions/node/v8.16.0/bin/node Yarn: 1.17.0 - /usr/local/bin/yarn npm: 6.13.2 - ~/.nvm/versions/node/v8.16.0/bin/npm Languages: Python: 2.7.10 - /usr/bin/python Browsers: Chrome: 78.0.3904.108 Firefox: 71.0 Safari: 13.0.1 npmPackages: gatsby: ^2.18.6 => 2.18.6 gatsby-cli: ^2.8.15 => 2.8.15 gatsby-image: ^2.0.37 => 2.2.34 gatsby-plugin-alias-imports: ^1.0.5 => 1.0.5 gatsby-plugin-eslint: ^2.0.4 => 2.0.8 gatsby-plugin-intl: ^0.1.7 => 0.1.7 gatsby-plugin-manifest: ^2.0.28 => 2.2.31 gatsby-plugin-offline: ^2.0.25 => 2.2.10 gatsby-plugin-react-helmet: ^3.0.12 => 3.1.16 gatsby-plugin-sharp: ^2.0.32 => 2.3.5 gatsby-plugin-sitemap: ^2.1.0 => 2.2.22 gatsby-source-filesystem: ^2.0.29 => 2.1.40 gatsby-source-graphql: ^2.1.26 => 2.1.26 gatsby-transformer-sharp: ^2.1.17 => 2.3.6 npmGlobalPackages: gatsby-cli: 2.7.2

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:31 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
herrwitzicommented, Dec 10, 2019

Can confirm aswell, works fine on 2.1.25 and breaks with 2.1.26

2reactions
alumezicommented, Feb 23, 2022

Hello guys this is happening to me on version 4.7.0?!

Screen Shot 2022-02-23 at 13 02 39 Screen Shot 2022-02-23 at 13 02 55
Read more comments on GitHub >

github_iconTop Results From Across the Web

error "gatsby-source-graphql" threw an error while running the ...
pluginName /[gatsby]/src/utils/api-runner-node.js:554:9 warning The gatsby-source-graphql plugin has generated no Gatsby nodes.
Read more >
gatsby-source-graphql
By default, gatsby-source-graphql executes each query in a separate network request. But the plugin also supports query batching to improve query performance.
Read more >
Error building with gatsby-source-prismic in the sourceNodes ...
When building I am receiving the following error: "gatsby-source-prismic" threw an error while running the sourceNodes lifecycle: a is not a ...
Read more >
“gatsby-source-airtable” threw an error while running the ...
Gatsby project compiles successfully on local but failed in netlify: Here is the complete log of deployment: Starting build script 10:25:06 ...
Read more >
My Gatsby site stopped working, and how I fixed it - Alex Nielsen
ERROR #11321 PLUGIN "gatsby-source-graphql" threw an error while running the sourceNodes lifecycle: warn The gatsby-source-graphql plugin has generated no ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found