Installed the gatsby-transformer-react-docgen plugin, but get this error message:
$ gatsby develop
success open and validate gatsby-config — 0.010 s
success load plugins — 0.238 s
success onPreInit — 0.783 s
success delete html and css files from previous builds — 0.017 s
success initialize cache — 0.017 s
success copy gatsby files — 0.069 s
success onPreBootstrap — 0.004 s
success source and transform nodes — 0.179 s
error UNHANDLED REJECTION
Error: Schema must contain unique named types but contains multiple types named "JSON".
- Array.forEach
- Array.forEach
- Array.forEach
- Array.forEach
- Array.forEach
- Array.forEach
If I remove the filesystem path to my components this error goes away, but the point is to read the components.
What could I be missing?
The repo to reproduce: https://github.com/mlibrary/umich-lib-components-react/tree/7a9e43c7900c74e5f9d881d3bfd044a4d8225be5
Still having this issue. Added a link to the repo to reproduce. @Chuloo
To fix this, we'd need to PR a fix to how the docgen transformer creates node type names. Anyone interested in doing this? I can give some pointers
@KyleAMathews I could take a look. Where should I start?
@KyleAMathews Still have this issue since August. A few others have 👍'd it. Could this be investigated?
Hiya!
This issue has gone quiet. Spooky quiet. 👻
We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
Thanks for being a part of the Gatsby community! 💪💜
Hey again!
It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
Thanks again for being part of the Gatsby community!
Still experiencing this issue with the latest package versions. I try every month or so to see if this works.
No resolution?
Most helpful comment
Still experiencing this issue with the latest package versions. I try every month or so to see if this works.