no socket.io.js in lib

[termie]

this breaks all existing users of this code and is a departure from the common pattern of putting your code in ./lib/

[rauchg]

Actually, this is the best pattern. This way, you can

require.paths.unshift('path/to/socket.io/lib')

and require it as a "singleton":

require('socket.io')

This way, we also achieve npm compatibility without enforcing it.

[termie]

the example code you just mentioned does not work, specifically due to the issue I described.