CHANGELOG.md

History

• 0.3.2 (Jan 2024)
• 0.3.1 (Jan 2024)
• 0.3.0 (Feb 2023)
• 0.2.1 (May 2022)
• 0.2.0 (Apr 2022)
• 0.1.0 (Jun 2021)

Release notes

0.3.2 (2024-01-23)

Bug Fixes

• add support for AWS DocumentDB (#21) (0c80f7f)
• ensure CSR works with a capped collection (d3fa038)
• exclude offline nodes when calling serverCount() (e2fb8c2)

0.3.1 (2024-01-10)

Bug Fixes

• add support for mongodb@6 (1a04885)
• properly handle promise rejections (075216f)

0.3.0 (2023-02-23)

Features

Connection state recovery

This adapter is now compatible with the connection state recovery feature, which was added in [email protected].

Reference: https://socket.io/docs/v4/connection-state-recovery

Added in 02e4d57.

Resume token

Upon reconnection to the MongoDB server, the client will now try to resume the stream at the last offset it has processed.

If the MongoDB client is disconnected for too long and its token is no longer valid, then the Socket.IO clients connected to this server may miss some packets (which was the previous behavior).

Added in e77063b.

0.2.1 (2022-05-03)

Bug Fixes

• properly handle invalidate events (938674d)

0.2.0 (2022-04-27)

Features

• add an option to use a TTL index (#4) (7fdbb25)

The addCreatedAtField option allows to use a TTL index instead of a capped collection, which is slightly less efficient but more predictable.

• broadcast and expect multiple acks (e87a0ce)

This feature was added in [email protected]:

io.timeout(1000).emit("some-event", (err, responses) => {
  // ...
});

Thanks to this change, it will now work with multiple Socket.IO servers.

• use a single stream for all namespaces (9b5f4c8)

The adapter will now create one single MongoDB stream for all namespaces, instead of one per namespace, which could lead to performance issues.

0.1.0 (2021-06-01)

Initial commit