-
Notifications
You must be signed in to change notification settings - Fork 365
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: move try catch to prepareServer #4732
Conversation
📊 Benchmark resultsComparing with 55d7013 Package size: 221 MB⬇️ 0.00% decrease vs. 55d7013
Legend
|
@eduardoboucas @danez I may have ran into a use case for the try/catch in prepareServer instead of initializeProxy (details in PR description). |
Can you help me understand what leads to this? If |
…ify/cli into fix/move-try-catch-to-prepareServer
@eduardoboucas this one's ready |
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 for submitting a pull request! 🎉
Summary
Related to #4621
netlify dev
before we have a chance to catch it in initializeProxy.For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)