Uncaught TypeError: Cannot read property 'socket' of undefined

[talmobi]

Halåj, this is a patch for a bug when a connection fails we are trying to access a property on the undefined result object instead of first handling the actual connection error.

Opened an issue for this also in case others have same problem: #19

fix for Uncaught TypeError: Cannot read property 'socket' of undefined

bugfix: Cannot read property 'socket' of undefined

error: Uncaught TypeError: Cannot read property 'socket' of undefined

description:
handle connection error first before attempting to get result.socket
result will be undefined if there is a connection error, and instead
of handling the connection error, we will crash on trying to reference
socket from an 'undefined' result object

[talmobi]

@TooTallNate I know you're busy, this is a very easy merge though~ thanks~

[knoxcard]

@JoshGlazebrook

[JoshGlazebrook]

@talmobi This line just needs to be moved under the check for err. No need for a try/catch, result.socket will always be defined if err is null.

Old:

var socket = result.socket
if (err) return fn(err);

New:

if (err) return fn(err);
var socket = result.socket

[TooTallNate]

Thank you, published as v4.0.1.