-
-
Notifications
You must be signed in to change notification settings - Fork 345
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
No indication of port being in use during provider.setup()
call?
#37
Comments
Thanks @screamish - seems like a nice UX addition! |
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
mefellows
added a commit
that referenced
this issue
Apr 16, 2017
feat(port-check): check if port is available during setup() #37
Latest build released to https://www.npmjs.com/package/pact ( For future me, I wasn't able to repro the Karma issue in the builds until I ran Thanks @screamish :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just spent a good while being a doofus getting started with pact-js in a new project (been a PACT user for a fair while) all because the port I chose for my provider (8081) was in use. Yes, my silly choice of port (if only I'd thought to run an
lsof
hours ago and save myself much wasted time), but I'm just wondering why this didn't result in error messages back fromprovider.setup()
or even anything in the debug level logs to console?The text was updated successfully, but these errors were encountered: