Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →

Sign in Demo Install

Sign in Demo Install

websocket-driver

Package Overview

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

websocket-driver - npm Package Versions

0.7.4

published 0.7.4 • 4 years ago

Changelog

0.7.4 / 2020-05-22

Avoid crashing if process.version does not contain any digits
Emit ping and pong events from the Server driver
Require http-parser-js >=0.5.1 which fixes the bug we addressed in 0.7.3

0.7.3

published 0.7.3 • 5 years ago

Changelog

0.7.3 / 2019-06-13

Cap version of http-parser-js below 0.4.11, which introduced a bug that prevents us from handling messages that are part of the same input buffer as the handshake response if chunked encoding is specified

0.7.1

published 0.7.1 • 5 years ago

Changelog

0.7.1 / 2019-06-10

Catch any exceptions produced while generating a handshake response and send a 400 Bad Request response to the client
Pick the RFC-6455 protocol version if the request contains any of the headers used by that version
Use the Buffer.alloc() and Buffer.from() functions instead of the unsafe Buffer() constructor
Handle errors encountered while handling malformed draft-76 requests
Change license from MIT to Apache 2.0

0.7.0

published 0.7.0 • 7 years ago

Changelog

0.7.0 / 2017-09-11

Add ping and pong to the set of events users can listen to
Replace the bindings to Node's HTTP parser with http-parser-js

0.6.5

published 0.6.5 • 8 years ago

Changelog

0.6.5 / 2016-05-20

Don't mutate buffers passed in by the application when masking

0.6.4

published 0.6.4 • 9 years ago

Changelog

0.6.4 / 2016-01-07

If a number is given as input for a frame payload, send it as a string

0.6.3

published 0.6.3 • 9 years ago

Changelog

0.6.3 / 2015-11-06

Reject draft-76 handshakes if their Sec-WebSocket-Key headers are invalid
Throw a more helpful error if a client is created with an invalid URL

0.6.2

published 0.6.2 • 9 years ago

Changelog

0.6.2 / 2015-07-18

When the peer sends a close frame with no error code, emit 1000

0.6.1

published 0.6.1 • 9 years ago

Changelog

0.6.1 / 2015-07-13

Use the buffer.{read,write}UInt{16,32}BE methods for reading/writing numbers to buffers rather than including duplicate logic for this

0.6.0

published 0.6.0 • 9 years ago

Changelog

0.6.0 / 2015-07-08

Allow the parser to recover cleanly if event listeners raise an error
Add a pong method for sending unsolicited pong frames