Add support for mocking WebSocket.bufferedAmount about jest-websocket-mock HOT 2 CLOSED

Glad to hear you like this library! :)

You can work around this Typescript issue by extending the WebSocket interface:

interface OverridableWS extends WebSocket {
  bufferedAmount: number;
}

const connection: OverridableWS = await server.connected;
connection.bufferedAmount = 100; // yay

I guess we could build this override in the library, but I'd like to avoid it unless there's a big demand for it. Currently, server.connected is the client instance, so I'd like to keep their types consistent.

Let me know if that answers your question / fixes your issue!

from jest-websocket-mock.

Thank you for the quick reply. Setting connection.bufferedAmount = 100 is affectless, as it's still zero afterward. For anyone else interested with the same use case, follows the workaround:

const connection = await server.connected;

const bufferedAmount = jest.fn()
    .mockReturnValueOnce(20)
    .mockReturnValueOnce(10)
    .mockReturnValueOnce(0);

Object.defineProperty(connection, 'bufferedAmount', {
    get: bufferedAmount,
});

from jest-websocket-mock.