5.0.1

Bug Fixes

• fix vite build (900346e)

Links

• Diff: 5.0.0...5.0.1

5.0.0

This release includes the migration to TypeScript. The major bump is due to the new "exports" field in the package.json file.

See also: https://nodejs.org/api/packages.html#packages_package_entry_points

Links

• Diff: 4.0.3...5.0.0

4.0.3

Bug Fixes

• respect the offset and length of TypedArray objects (6d7dd76)

Links

• Diff: 4.0.2...4.0.3

4.0.2

Bug Fixes

• add base64-arraybuffer as prod dependency (2ccdeb2)

Links

• Diff: 4.0.1...4.0.2

2.2.1

Links

• Diff: 2.2.0...2.2.1

4.0.1

Links

• Diff: 4.0.0...4.0.1

4.0.0

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)

Links

• Diff: v4.0.0-alpha.1...4.0.0
• Full diff: 2.2.0...4.0.0

v4.0.0-alpha.1

Features

• implement the version 4 of the protocol (cab7db0)

Links

• Diff: v4.0.0-alpha.0...v4.0.0-alpha.1

v4.0.0-alpha.0

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>

Links

• Diff: 2.2.0...v4.0.0-alpha.0

Release 2.2.0

Performance enhancements

We now use Buffer.allocUnsafe() and Buffer.from() methods instead of manually creating the buffer instances. (#104 & #108)

Thus support for Node.js 4 is dropped (since Buffer.allocUnsafe was added in v5.10.0).

Diff: 2.1.3...2.2.0