-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(gatsby): fix error cannot read referencePath of undefined #20517
fix(gatsby): fix error cannot read referencePath of undefined #20517
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Left a small suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much!
I (kind of) have the same error:
But applying the changes from this PR doesn't seem to fix it... Would you an idea? Thanks in advance |
Thats a different error This PR fix an error in |
It would be very helpful if you open an new issue with the new error |
@adrienharnay, I had something similar then managed to get it working with a fresh package install and deleting the |
@adrienharnay please look at PR #20730 - maybe this PR fix your problem |
Hey, actually it was an opaque error from gatsby-source-graphql... So not related, sorry. |
Description
fixes an error in the file
find-api-calls.js
:since the file
api-runner-node-error-parser.js
is an helper function and not need a link to the source i assume it can be fixed with a "monkey patch": renaming the file:from:
api-runner-node-error-parser.js
to:
api-runner-error-parser.js
see #20488
Related Issues
fixes #20488