josephg
move package to pure js
As discussed, node-browserchannel may eventually be ported from coffeescript to javascript. If this happens, coffeescript would continue to be used for the test suite.
The coffeescript should be compiled to javascript, and the javascript should be cleaned up manually in small commits. At no point should the test suite be broken.
... I'm currently working through a couple of changes in the 2.0 branch to make browserchannel use node streams & closer fit the websocket API. Hold off on porting it to JS for a week or two.
Figured this would stay in the backlog for a bit. Marked #23 as ready. If you add the other features as issues as well, I'll keep an eye on the waffle.
I ported the client to closurey javascript in a branch. It has a couple of bugs - and generally I'm not super happy with the result. It looks a lot harder to maintain...
Thanks @Dashed I've been meaning to check out babel for some time. This might be a good excuse to try out some es6
So you want to move from one compile language straight into something else that requires compilation?
lol @3rd-Eden assuming the expectation is that es6 eventually won't require compilation, but that is a ways off
can I require the client in a babel-compiled front-end application currently?
