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.
How to debug a source plugin on Gatsby side?
See original GitHub issueSummary
I am using the plugin gatsby-source-datocms and I faced that createNodeField doesn’t create anything. I believe it is not related to the Gatsby side but I would like to know how can I trace down the root cause of my additional fields can’t be queried.
I would like to place some logs on the Gatsby side to see the node content, after it is processed by the plugin.
Reference: https://github.com/datocms/gatsby-source-datocms/issues/92
Relevant information
Environment (if relevant)
File contents (if changed)
gatsby-config.js: N/A
package.json: N/A
gatsby-node.js: N/A
gatsby-browser.js: N/A
gatsby-ssr.js: N/A
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks @Js-Brecht
After I changed the last
infer: falsetoinfer: truein https://github.com/datocms/gatsby-source-datocms/blob/master/src/hooks/sourceNodes/createTypes/item/index.jsI can see my added field in GraphQL.
I would suggest moving that issue to the plugin repo then as it doesn’t seem to be an issue with Gatsby - and the initial question was answered. Thanks!