[lprnmns]

Both the client and the server answer a ping with a pong that echoes the ping's payload, but that pong is the only message they serialize without jsonMessageReplacer. Every other message (connection_init, connection_ack, subscribe, next, error, complete) already passes it.

This matters when the reviver and replacer are a pair. For example, with a reviver that turns a field into a BigInt and a replacer that turns it back into a string, the revived ping payload can't be serialized for the pong: JSON.stringify throws "Do not know how to serialize a BigInt", and the connection gets closed.

The fix passes replacer to stringifyMessage for the automatic pong in src/server.ts and src/client.ts.

Tests: one new test in tests/server.test.ts and one in tests/client.test.ts, each sending a ping with a payload that the reviver turns into a BigInt. Both fail on master (the server test gets no pong, and the client closes the socket) and pass with this change. The full suite, tsc --noEmit and Prettier pass. A patch changeset is included.

[enisdenjo]

🙏