Releases: lukeed/sockette
Releases · lukeed/sockette
v2.0.4
10 Dec 19:18
Compare
Sorry, something went wrong.
No results found
Patches
Fix: Remove fat-arrow function for complete ES5 compliance (#41 ): 7ff9780
v2.0.3
14 Nov 03:15
Compare
Sorry, something went wrong.
No results found
Patches
Add default protocols for Firefox (#20 ): a465457
Thanks @Inva0 !
Allow reconnect() to continue when no connection can establish on init (#30 ): 14424e4
Ensure code=1005 default when close()ing without arguments (#36 ): 5102793 , d935a48
Chores
v2.0.2
13 Nov 22:01
Compare
Sorry, something went wrong.
No results found
Features
Patches
Use .mjs extension for ES Module entry: bc08862
Chores
v2.0.1
13 Nov 21:58
Compare
Sorry, something went wrong.
No results found
v2.0.0
12 Feb 22:07
Compare
Sorry, something went wrong.
No results found
Breaking
You must now instantiate an instance rather than functional helper: 0a9c339
const Sockette = require ( 'sockette' ) ;
// Don't:
let ws = Sockette ( '...' ) ;
// Do:
let ws = new Sockette ( '...' ) ;
Sockette no longer returns the underlying WebSocket: 0a9c339
Instead, it returns itself, keeping the current WebSocket instance protected and out of reach.
Returning the WebSocket prevented the ability to send new messages after successful reconnects.
Minor
NEW: Added opts.onmaximum callback (#11 ): 712defb , e59b0e7
This is called when the maxAttempts have been exhausted.
Patches
Fixed transmits from Sockette after reconnecting/recovering from failure: 0a9c339
By hiding the underlying WebSocket, Sockette can safely swap/update instances without invalidating your pointer to initial WebSocket return.
A successful reconnection will reset the tracked attempts count: 6d8095a
Previously, reconnecting after 6 attempts only left you 4 attempts for your next connection failure — assuming a limit of 10.
Update README docs: b9d74b0 , e656e08 , 556fe3e , e59b0e7
v1.2.0
01 Feb 19:00
Compare
Sorry, something went wrong.
No results found
Minor Changes
Patches
Update docs for json() addition: 117f06d
v1.1.0
31 Jan 09:44
Compare
Sorry, something went wrong.
No results found
Minor Changes
Don't auto-enforce a close(1000): f8771f0
As @lpinca pointed out, this is non-compliant behavior to the WS spec, and I was porting/pulling too much from personal use cases.
Patches