@svk it builds under browserify, on a clean checkout however the websocket library you're using is native code and not pure js, this may keep it from running. I can't think of a reason to use native code for websockets anymore. Is this just dependency hell or was it something specific this lib brings to the table?
More info on this BTW
http://stackoverflow.com/questions/29741158/how-to-use-websocket-npm-library-in-browser
The library uses a node web socket library for use in Node.js since there's no native websocket support there. But in browsers it will use the built in websocket but wrapped with ReconnectingWebsocket. Is that what you meant?
@svk actually that might be what I meant, I just remember there being issues with node websocket under browserify. Haven't had my morning coffee yet though.
JS isn't my daily language anymore.
@svk I'm going over your library with a fine toothed comb and a couple interns.
I'd very much like to thank you for this library. It's as close to perfect as I've seen JS come. You rocked this stuff. Even I'm learning new things from it. I especially like how you don't import the kitchen sink into everything. Great work!