Closed derekr closed 6 years ago
I was able to recreate this issue from @derekr's report above. I thought maybe the plugin was failing due to there being no docgen blocks, but adding a docblock to the src/components/Header
component doesn't make any difference to the console output.
Ah! I was about to pass on this, but it looks like the build will work as long as one of your components has some PropTypes defined. I can see this would be a pretty frustrating problem..
@KyleAMathews or @jquense is it possible to add some logging around this?
Thanks for following up @m-allanson! Confirmed the propTypes
work around. Some logging would be rad. I could take a look at it some time next week if no one hops on it.
Huh weird. Yeah, we should either log and/or just work around the lack of data from not having propTypes
As this is graphql schema related I will have a look. Is there fast way to reproduce it?
I'm getting the exact same error using the datocms-source plugin
https://github.com/datocms/gatsby-source-datocms/issues/11
Have cloned their portfolio repo and getting the same error
added proptypes to the header component but doesn't work :(
Due to the high volume of issues, we're closing out older ones without recent activity. Please open a new issue if you need help!
Description
When using
gatsby-transformer-react-docgen
I get anerror UNHANDLED REJECTION
error during the source and transform stage.Environment
Gatsby version:
^1.9.158
Node.js version:v9.5.0
Operating System:OSX 10.13.3
File contents (if changed):
gatsby-config.js
:package.json
:gatsby-node.js
: not changedgatsby-browser.js
: not changedgatsby-ssr.js
: not changedActual result
Expected behavior
Development server starts and I can query as expected for the react docgen transformer.
Steps to reproduce