Repository navigation
Local plugin development #51
Answered
by
Js-Brecht
openscript
asked this question in
Q&A
|
Hello community Is it possible that this issue is related to gatsby-plugin-ts-config? I'm a bit stuck here. Has someone an idea how to debug this further? Thank you! Robin |
Answered by
Js-Brecht
Oct 11, 2021
Replies: 1 comment
|
No, those modules are hit by Webpack during the build. Also, this looks like an error generated by React itself, rather than a compiler generated error. I would start by spinning it up in the debugger and breaking inside of |
0 replies
Answer selected by
openscript
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No, those modules are hit by Webpack during the build.
gatsby-plugin-ts-configis entirely bootstrap (before the bootstrap even, if we’re being exact).Also, this looks like an error generated by React itself, rather than a compiler generated error.
I would start by spinning it up in the debugger and breaking inside of
wrapPageElementso you can see whatelementactually is (as well as the rest of the provided props in that first parameter). That might give you a clue what is actually being provided to your function