-
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: handle node api-api error gracefully #9255
Conversation
@@ -243,13 +242,8 @@ module.exports = async (api, args = {}, pluginSource) => | |||
) | |||
}) | |||
.catch(err => { |
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.
it seems like this catch should be for individidual plugin API call and not for Promise.mapSeries
. It makes using pluginName
a bit weird there (fact that it needs to be declared early) plus maybe it would allow for easier recovery in develop?
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.
(and also returning null
would actually make sense there)
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.
ah probably yes, that's a better option 👍
Thanks! Sorry for the poor formatting I meant to fix it and got pulled away :/ |
I keep getting weird errors and it was because my gatsby-node.js had issues, but the build was continuing assuming there was a `result`
I keep getting weird errors and it was because my gatsby-node.js had issues, but the build was continuing assuming there was a `result`
I keep getting weird errors and it was because my gatsby-node.js had issues, but the build was continuing assuming there was a
result