We just published two fixes for socket.io-client:
Building with browserify or webpack is now completely straightforward. No need to exclude/ignore or noParse/externals the ws module.
Improved the JSONP transport when socket.io-client or engine.io-client are lazily evaluated or the <script> tag that included them gets removed.
We published three minor releases right after 1.4.0 addressing build issues in different environments.
Socket.IO 1.4.0 ship with new features like automatic compression for XHR and WebSockets, lots of bug fixes and significant performance and memory improvements.
Socket.IO 1.3.7 includes support for io.js and Node.JS 4.0.0.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.7/socket.io.min.js"></script>Socket.IO 1.3.6 addresses a build issue with the ws module on Windows.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.6/socket.io.min.js"></script>
Today were very happy to introduce Socket.IO P2P, the easiest way to establish a bidirectional events channel between two peers with a server fallback to provide maximum reliability.
I'm really proud to announce the first release of the Socket.IO C++ Client on GitHub!
We are pleased to announce the immediate availability of the Socket.IO Swift Client! Youll now be able to write code that runs natively on iOS and OSX, while maintaining the simplicity and expressiveness of the JavaScript client!
Socket.IO 1.3.5 addresses a parser issue. Upgrade recommended. Completely backwards-compatible.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.5/socket.io.min.js"></script>Socket.IO 1.3.4 corrects the 1.3.3 build that included extra unused code.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.4/socket.io.min.js"></script>