v1.1.0 doesn't work with grunt-contrib-connect

[alippai]

The last portscanner release broke our connect tasks saying "Fatal error: Port 443 is already in use by another process.".

[philtim]

We had the very same problem. Try changing your port number from a string to a number. The latest version now checks whether the params are of type number, string, or function and handles each one differently. Surely not a nice solution, but a quick workaround.

[laggingreflex]

Extremely sorry about introducing a breaking change in a minor version.

I've reverted it to 1.0.0 which is now published as 1.1.1

The previous new version is now published as 2.0.0

[laggingreflex]

I'm trying to hunt down what's causing the error, could you please let me know how you're using grunt-contrib-connect? I've ran its tests with portscanner 1.1.0 and they seem to be all passing.

[laggingreflex]

Thanks very much for the insight @philtim. Hopefully fixed now. See #51 for details