It just so happens that only like 5 minutes ago I added a browserify build for natebrune in steemit.chat, you can find it here:
https://github.com/svk31/steemjs-lib/tree/master/build
Now it's certainly a work in progress as I haven't actually tested it myself yet, I'll see if I can add an example html file using it later today or tomorrow.
Well I'm working on this bounty too and saw your browserify build come across right after I pulled your code in to look at doing exactly that.
Want me to test it for you while I'm in here?
Feel free to use whatever you want from my code. The code from steemit.com is surely more robust but mine might be easier to work with since it's in library form.
If you feel like testing it then yea go for it :)
@svk yeah that and you know what a comment looks like and aren't afraid to use it :D
So what @pharesim is asking for here is a flat project that doesn't need npm or browserify.
Obviously that's going to be a lot of work, but it is something that can be done by a team of 4 or so reasonably competent people in a couple of days.
Mostly a matter of normalizing all these libraries built for node into something browser compatible without resorting to browserify or npm.
If anyone wants to join in on getting this built for him I'm more than willing to split the bounty equally with everyone. I had assumed it was just a typedbuffer issue, but it's a lot more indepth than that.
@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!