-
Notifications
You must be signed in to change notification settings - Fork 27.8k
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
Automatically select port when starting #358
Comments
I am currently using this technique on a project (Phenomic) and I can tell the UX is not the best. Especially if you are already using your own project, just in another terminal/tab and you forget it. create-react-app is doing something different and tells you that something (and who) is using the port and offer you a way to adjust it. |
Totally agree! The UX you proposede is in fact better than automatically selecting another port. The thing that is actually bugging me is thatt next.js does not reflect the fact 3000 is already in use, and thus creates output that is simply not correct/misleading. |
Related discussion: #68 |
Oh that's exactly this. I guess this issue can be closed then? |
I hope so. Let's talk more on that PR. |
When starting next outputs this:
Even if something else is already running on 3000. It would be great if next could detect that and then automatically use the next sensible free port (e.g. 3001).
The text was updated successfully, but these errors were encountered: