-
Notifications
You must be signed in to change notification settings - Fork 28
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
Is it possible to use next available port? #15
Comments
OK, I will make it try to get next port 10 times. |
fengmk2
added a commit
that referenced
this issue
Mar 17, 2017
fengmk2
added a commit
that referenced
this issue
Mar 17, 2017
fengmk2
added a commit
that referenced
this issue
Mar 17, 2017
* fix: try to use next available port closes #15 * test: use egg-bin for test on node v4
@gaearon Please take a try on detect-port@1.1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before updating to 1.1.0,
detect-port
used to suggest the next available port (e.g. 3001 if I requested 3000 but it is busy). Now, it seems to always suggest random ports (e.g. I just got 49655).Is it possible to preserve the old behavior of suggesting the next available port, or are there any downsides?
The text was updated successfully, but these errors were encountered: