streaming sockjs for node and the browser
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
node_modules/sockjs-client vendored sockjs-client Jul 26, 2013
test tests work with testling@1.4.1 finally Jul 26, 2013
.npmignore 0.0.10 Mar 16, 2013
LICENSE working example Jun 23, 2012
browser.js browser.js now checks for a protocol before attempting to resolve Aug 29, 2013
index.js stream should ALWAYS emit close Aug 26, 2013
package.json 0.0.15 Aug 29, 2013



Streaming sockjs for node and the browser.

This is a more streaming, more unixy take on sockjs.

shoe point javascript


stream all the things

Browser code that takes in a stream of 0s and 1s from the server and inverts them:

var shoe = require('shoe');
var through = require('through');

var result = document.getElementById('result');

var stream = shoe('/invert');
stream.pipe(through(function (msg) {

Server code that hosts some static files and emits 0s and 1s:

var shoe = require('shoe');
var http = require('http');

var ecstatic = require('ecstatic')(__dirname + '/static');

var server = http.createServer(ecstatic);

var sock = shoe(function (stream) {
    var iv = setInterval(function () {
        stream.write(Math.floor(Math.random() * 2));
    }, 250);
    stream.on('end', function () {
    stream.pipe(process.stdout, { end : false });
sock.install(server, '/invert');

The server emits 0s and 1s to the browser, the browser inverts them and sends them back, and the server dumps the binary digits to stdout.

By default, there's no logspam on stdout to clutter the output, which is a frustrating trend in realtimey websocket libraries that violates the rule of silence.

Just wait for a client to connect and you'll see:

$ node server.js

with dnode

Since dnode has a simple streaming api it's very simple to plug into shoe.

Just hack up some browser code:

var shoe = require('shoe');
var dnode = require('dnode');

var result = document.getElementById('result');
var stream = shoe('/dnode');

var d = dnode();
d.on('remote', function (remote) {
    remote.transform('beep', function (s) {
        result.textContent = 'beep => ' + s;

and hack up a server piping shoe streams into dnode:

var shoe = require('shoe');
var dnode = require('dnode');

var http = require('http');
var ecstatic = require('ecstatic')(__dirname + '/static');

var server = http.createServer(ecstatic);

var sock = shoe(function (stream) {
    var d = dnode({
        transform : function (s, cb) {
            var res = s.replace(/[aeiou]{2,}/, 'oo').toUpperCase();
sock.install(server, '/dnode');

Then open up localhost:9999 in your browser and you should see:

beep => BOOP

with express or connect

you must pass the return value of app.listen(port)

var shoe = require('shoe');

var express = require('express')
var app = express()

var sock = shoe(function (stream) { ... });

// *** must pass expcess/connect apps like this:
sock.install(app.listen(9999), '/dnode');

with reconnect

you can use reconnect just in case your sock ends or gets disconnected.

var shoe = require('shoe');
var reconnect = require('reconnect');
var es = require('event-stream');
var result = document.getElementById('result');

var r = reconnect(function (stream) {

  var s = es.mapSync(function (msg) {
      return String(Number(msg)^1);


browser methods

var shoe = require('shoe')

var stream = shoe(uri, cb)

Return a readable/writable stream from the sockjs path uri. uri may be a full uri or just a path.

shoe will emit a 'connect' event when the connection is actually open, (just like in net). writes performed before the 'connect' event will be buffered. passing in cb to shoe is a shortcut for shoe(uri).on('connect', cb)

server methods

var shoe = require('shoe')

All the methods from the sockjs exports objects are attached onto the shoe function, but the shoe() function itself is special.

var sock = shoe(opts, cb)

Create a server with sockjs.createServer(opts) except this function also adds the .install() function below.

If cb is specified, it fires cb(stream) on 'connection' events.

sock.install(server, opts)

Call sock.installHandler() with the default option of spamming stdout with log messages switched off in place of just emitting 'log' messages on the sock object instead. This is a much less spammy default that gets out of your way.

If opts is a string, use it as the opts.prefix.

server events

All the messages that sockjs normally emits will be available on the sock object plus the events below:

sock.on('log', function (severity, msg) { ... })

Using the default logger with sock.install() will cause these 'log' messages to be emitted instead of spamming stdout.


With npm do:

npm install shoe