Canop opened this issue 10 years ago · 1 comments
This is due to the fact that, last time I checked, socket.IO 1.0.x wasn't available through npm. There should be a clean way to fix that though.
The socket.IO repository is now up to date. I'll fix the package.json file.