Skip to content
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

Closed
kazzkiq opened this issue May 13, 2018 · 4 comments
Closed

Force use port #365

kazzkiq opened this issue May 13, 2018 · 4 comments

Comments

@kazzkiq
Copy link

kazzkiq commented May 13, 2018

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 with serve, if I configure my proxy to forward requests to port 5000, but suddenly serve 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.

@leo
Copy link
Contributor

leo commented May 28, 2018

This is now the default!

As described in the notes for the new release.

@leo leo closed this as completed May 28, 2018
@jespertheend
Copy link
Contributor

@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.

@jespertheend
Copy link
Contributor

#490 👀

@pskelin
Copy link

pskelin commented Mar 25, 2021

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.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants