Closed alippai closed 5 years ago
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.
Seems to be fixed upstream.
The latest portscanner release breaks the current grunt-contrib-connect version: https://github.com/baalexander/node-portscanner/issues/49