Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 

3.3 KiB

4.0.1 (2020-09-10)

Bug Fixes

  • use a terser-compatible representation of the separator (886f9ea)

4.0.0 (2020-09-08)

This major release contains the necessary changes for the version 4 of the Engine.IO protocol. More information about the new version can be found there.

Encoding changes between v3 and v4:

  • encodePacket with string

    • input: { type: "message", data: "hello" }
    • output in v3: "4hello"
    • output in v4: "4hello"
  • encodePacket with binary

    • input: { type: 'message', data: <Buffer 01 02 03> }
    • output in v3: <Buffer 04 01 02 03>
    • output in v4: <Buffer 01 02 03>
  • encodePayload with strings

    • input: [ { type: 'message', data: 'hello' }, { type: 'message', data: '€€€' } ]
    • output in v3: "6:4hello4:4€€€"
    • output in v4: "4hello\x1e4€€€"
  • encodePayload with string and binary

    • input: [ { type: 'message', data: 'hello' }, { type: 'message', data: <Buffer 01 02 03> } ]
    • output in v3: <Buffer 00 06 ff 34 68 65 6c 6c 6f 01 04 ff 04 01 02 03>
    • output in v4: "4hello\x1ebAQID"

Please note that the parser is now dependency-free! This should help reduce the size of the browser bundle.

Bug Fixes

  • keep track of the buffer initial length (8edf2d1)

Features

  • restore the upgrade mechanism (6efedfa)

4.0.0-alpha.1 (2020-05-19)

Features

  • implement the version 4 of the protocol (cab7db0)

4.0.0-alpha.0 (2020-02-04)

Bug Fixes

  • properly decode binary packets (5085373)

Features

  • remove packet type when encoding binary packets (a947ae5)

BREAKING CHANGES

  • the packet containing binary data will now be sent without any transformation

Protocol v3: { type: 'message', data: <Buffer 01 02 03> } => <Buffer 04 01 02 03> Protocol v4: { type: 'message', data: <Buffer 01 02 03> } => <Buffer 01 02 03>

2.2.0 (2019-09-13)

  • [refactor] Use Buffer.allocUnsafe instead of new Buffer (#104) (aedf8eb), closes #104

BREAKING CHANGES

  • drop support for Node.js 4 (since Buffer.allocUnsafe was added in v5.10.0)

Reference: https://nodejs.org/docs/latest/api/buffer.html#buffer_class_method_buffer_allocunsafe_size