-
Notifications
You must be signed in to change notification settings - Fork 25
Library not detecting port is in use #17
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
Comments
Oh and I'm on a macOS Sierra 10.12.3 |
I met the same issue while I run my project on |
I got the same issue, and [email protected] works. |
Maybe bug here, I will check it and fix it today. |
Bug is actually here https://github.com/node-modules/detect-port/blob/master/lib/detect-port.js#L47 I fixed it in my project like this: https://github.com/d4rkr00t/aik/blob/master/src/utils/detect-port.js#L12 Basically you need to specify a host. |
I'm using this lib with Gatsby having borrowed the idea from create-react-app. It had been working great but it's now for whatever reason not detecting used ports.
I start a gatsby instance on port 8000 and then another and detect-port tells me 8000 is open but when gatsby tries starting in the second instance, it gets an
EADDRINUSE
.I've tried this on node 6 and 7.
Does it matter that Gatsby is listening on 0.0.0.0?
The text was updated successfully, but these errors were encountered: