You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Bouncey can you try upgrading gatsby and dependencies to their latest stable versions? We released version 2 recently, that might solve the issue for you.
<!--
Q. Which branch should I use for my pull request?
A. Use `master` branch (probably).
Q. Which branch if my change is a bug fix for Gatsby v1?
A. In this case, you should use the `v1` branch
Q. Which branch if I'm still not sure?
A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)
Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.
Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
Closes#6771
gpetrioli
pushed a commit
to gpetrioli/gatsby
that referenced
this issue
Jan 22, 2019
…yjs#9839)
<!--
Q. Which branch should I use for my pull request?
A. Use `master` branch (probably).
Q. Which branch if my change is a bug fix for Gatsby v1?
A. In this case, you should use the `v1` branch
Q. Which branch if I'm still not sure?
A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)
Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.
Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
Closesgatsbyjs#6771
Description
Development proxy request errors cause
gatsby
to crash due to an unhandled exception.It would be nice to keep the
gatsby develop
process alive to test site failoverSteps to reproduce
Any
gatsby
site with with a development proxy provided ingatsby-config.js
.If the proxy url provided is set to fail (proxy server not running, invalid url),
gatsby develop
will crash when a request is made to the proxy.Expected result
Exceptions should be handled and reported to the developer.
gatsby develop
process remains alive.Actual result
gatsby develop
process exits on an unhandled exception.Environment
gatsby info --clipboard
not available in v1?File contents (if changed)
Shouldn't be required
gatsby-config.js
: N/Apackage.json
: N/Agatsby-node.js
: N/Agatsby-browser.js
: N/Agatsby-ssr.js
: N/ANotes
I have tried wrapping
req.pipe(request(proxiedUrl)).pipe(res)
in atry...catch
, but the error slips through.The text was updated successfully, but these errors were encountered: