Doesn't work with portscanner@1.1.0
alippai opened this issue · 2 comments
alippai commented
The latest portscanner release breaks the current grunt-contrib-connect version:
baalexander/node-portscanner#49
philtim commented
portscanner@1.1.0 now checks whether the port number is a number, string, or function and handles each type differently. In our case it was sufficient to change the port number from a string into a number.
XhmikosR commented
Seems to be fixed upstream.