Netlify Dev isn’t working with the --live flag, it throws a ValidationError: ‘port’ is required. I looked through this post but that’s not my problem, because it works fine without the --live flag. Maybe in the 2.42 fix for it mentioned here they missed the --live option?
Here’s the error message
It’s a Gatsby site.
Thank you for reporting this @jcaguirre89 . We’ve identified the problem and a fix has been proposed. Please hold on while release it.
netlify:master ← netlify:raees/fix-live
opened 05:26PM - 16 Apr 20 UTC
<!--
Thanks for submitting a pull request!
Please make sure you've read and … understood our contributing guidelines;
https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx", where #xxxx is the issue number.
Please provide enough information so that others can review your pull request.
The first three fields are mandatory:
-->
**- Summary**
We broke this perviously by not returning `proxyPortUsed` from `startProxy`.
Fixes: https://github.com/netlify/cli/issues/797
Fixes: https://community.netlify.com/t/netlify-dev-live-flag-failing-port-is-required/12543
<!--
Explain the **motivation** for making this change.
What existing problem does the pull request solve?
-->
**- Test plan**
`netlify dev --live` in your project
<!--
Demonstrate the code is solid.
Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
-->
**- Description for the changelog**
Use `settings.proxyPort` instead of expecting `proxyPortUsed` from `startProxy`
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
**- A picture of a cute animal (not mandatory but encouraged)**
🐰
1 Like
