Updated readme to add port number when testing a site with authentication

[mikerhyssmith]

fixes #2404

[patrickhulce]

maybe add a note that it's 9222 by default or use it as the example port?

[brendankenny]

wait, wasn't the whole point that chrome-debug now uses a random port and doesn't have a default?

[patrickhulce]

now uses a random port and doesn't have a default?

I thought Lighthouse was looking to launch one on a random port but the instructions told you to open one already at 9222?

[patrickhulce]

Oh no it tells you to use chrome-debug nevermind ignore me :) why don't we default chrome-debug to 9222 then?

[paulirish]

why don't we default chrome-debug to 9222 then?

I made that call. Mostly because it's possible of a port conflict and I wanted to make sure that chrome-debug command always works even if you have a second one already launched.

The output now says what port it's on, so it seems kinda reasonable to ask the user to use that port.

wdyt

[mikerhyssmith]

Is it worth adding a note in the readme that chrome-debug will log the port its running on to then use in the lighthouse command ?

[patrickhulce]

aight carry on then @mikerhyssmith that sounds good to me :)

[paulirish]

Is it worth adding a note in the readme that chrome-debug will log the port its running on to then use in the lighthouse command ?

yup. let's do that :)