substack/dnode — pull request #90 by timoxley (2012-02-08 06:27:06+00:00)
Title: Handle errory connection string

Currently, if you pass an invalid string to dnode.connect, it will give you a terribly uninformative error message:

eg

```
TypeError: Cannot read property 'end' of undefined
at createClient (/Users/secoif/Projects/groupdock/libs/capre/node_modules/dnode/index.js:241:24)
at attachDnode (/Users/secoif/Projects/groupdock/libs/capre/node_modules/dnode/index.js:103:18)
at EventEmitter.connect (/Users/secoif/Projects/groupdock/libs/capre/node_modules/dnode/index.js:62:9)

```

This patch emits a slightly more informative message, although there doesn't appear to be a way to catch it other than try catch around the code. :(