-
Notifications
You must be signed in to change notification settings - Fork 693
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
Force use port #365
Comments
This is now the default! As described in the notes for the new release. |
@leo Is this still the case? I'm on 11.3.0 but I'm still getting a message that a different port is used. |
#490 👀 |
Can we please get an npm version with this feature? It would be great to use it directly from npm instead of referencing github urls. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to force serve to use a port, and if its already being used, it just throws?
The behavior of simply picking another port may be troublesome in some cases, like when you have other things depending on this first server listening on the right port.
An example of this is using
micro-proxy
withserve
, if I configure my proxy to forward requests to port5000
, but suddenlyserve
decided it was a good idea to pick another port without halting/throwing, it may lead to odd behavior and hard to catch bugs, because I'm basically listening the wrong server.The text was updated successfully, but these errors were encountered: