-
Notifications
You must be signed in to change notification settings - Fork 352
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(command-dev): use waitPort built-in http request support #2842
Conversation
📊 Benchmark resultsComparing with 94f64a4 Package size: 331 MB(no change)
Legend
|
@@ -93,35 +86,12 @@ const startFrameworkServer = async function ({ settings, log, exit }) { | |||
port: settings.frameworkPort, | |||
output: 'silent', | |||
timeout: FRAMEWORK_PORT_TIMEOUT, | |||
...(settings.disableLocalServerPolling ? {} : { protocol: 'http' }), |
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.
This option is documented via the library types and somehow here too.
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.
@eduardoboucas can you verify this doesn't break the original fix (I remember you had issues with this when running create-react-app
).
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.
@eduardoboucas can you verify this doesn't break the original fix (I remember you had issues with this when running
create-react-app
).
It seems to work fine! I remember the issue was with a Gatsby site and I'm not able to replicate it using this branch.
- Summary
Related to #1704
Uses
waitPort
built in support for testingHTTP
requests instead of polling ourselves.- Test plan
Existing tests, I'll verify with various frameworks manually too.
- A picture of a cute animal (not mandatory but encouraged)
😼