-
Notifications
You must be signed in to change notification settings - Fork 289
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(jest-dev-server): fix port detection #518
Conversation
Hi @gregberge did these changes build correctly into I'm still seeing the old Thanks |
@colinrotherham just redeployed, I checked the code and it is correct. |
@gregberge That's great, thank you. Appreciate it We had a Dependabot update for |
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
Port detection has now been fixed in `jest-dev-server`: argos-ci/jest-puppeteer#518
err.code === "EADDRINUSE" ? resolve(cleanupAndReturn(true)) : reject() | ||
) | ||
.once("listening", () => resolve(cleanupAndReturn(false))) | ||
.listen(config.port, config.host); |
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.
Fix #460, #281, #233