NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #2138 most downloaded on npm
SockJS-node is a server counterpart of SockJS-client a JavaScript library that provides a WebSocket-like object in the browser. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication
Latest stable
0.3.24
Last release 5 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 2.4 years
Nearly every release is documented
notes for 34 of 34 stable releases
Nothing withdrawn
no release was ever pulled
15 years old
36 releases · first in 2011
Drag across the ruler to compare, or tap a release to open it.
Remove excess file from npm package
Fix uuid usage
uuid usageUpdate uuid
uuidYour coding agent can read these notes before it upgrades. Set up the MCP server →
Update faye-websocket and websocket-driver to address DDoS vulnerability #275
faye-websocket and websocket-driver to address DDoS vulnerability #275Updated node-uuid and coffeescript
Add disable_cors option to prevent CORS headers from being added to responses #218
Change to using res.statusCode instead of manual parsing of res._header #213
Fix usage of undefined session in heartbeat_timeout #179
session in heartbeat_timeout #179Fix CORS response for null origin #177
no-transform to Cache-Control headers #189- #175 - Remove usage of naked '@' function params to be compatible with coffeescript 1.9.0
Re-publish to npm because of build issue in 0.3.13
- #171 - upgrade faye-websocket to 0.9.3 to fix growing FD count
Allow Faye socket constructor options to be passed with faye_server_options option to createServer
* #133 - only delay disconnect on non-websocket transports * Upgrade Faye to 0.8.0
Get rid of need for _sockjs_onload global variable
Upgrade Faye to 0.7.2 from 0.7.0
Upgrade Faye to 0.7.0 from 0.4.0
Expose "protocol" on raw websocket connection instance, correctly
When the server closes a connection, make sure the send buffer still gets flushed.
* #103 - connection.protocol might have been empty on some rare occasions. * #99 - faye-websocket was leaking sockets in "closed" state when dealing w
remove 'optionalDependencies' section from package.json, 'rbytes' was always optional.
sockjs/sockjs-protocol#56, #88 Fix for iOS 6 caching POSTs
Running under node.js 0.7 caused infinite recursion (Stephan Kochen)
Sending JSESSIONID cookie is now *disabled* by default.
Bumped "faye-websocket" dependency to 0.4. Updated code to take advantage of introduced changes.
Dropped deprecated Server API (use createServer method instead).
websocket is now used instead of disabled_transports.* #27 - Allow all unicode characters to be send over SockJS. * #14 - Make it possible to customize JSESSIONID cookie logic.
* #32 Expose various request headers on connection. * #30 Expose request path on connection.
The API changed, there is now an idiomatic API, modelled on node.js Stream API. The old API is deprecated and there is a dummy wrapper that emulates i…
Server constructor: log,
heartbeat_delay and disconnect_delay.write is converted to a string.Connection.remoteAddress property introduced (Stéphan Kochen)* #20: npm submodule sockjs didn't work due to outdated github path.
npm submodule sockjs didn't work due to outdated github
path.Support for htmlfile transport, used by IE in a deployment dependent on cookies.
EventSource transport didn't emit 'close' event.
By default set JSESSIONID cookie, useful for load balancing.
* Initial release.
Nothing published for this version
Nothing published for this version
One column per quarter.