socket.removeEventListener('close',..) not present in 4.1.2, (maybe) reason for MaxListenersExceededWarning from Node about graphql-ws

[enisdenjo]

Hey hey, thanks for reporting this issue! Nope, I am indeed subscribing to the same event on each subscription which causes Node to raise this warning. As you may noticed I am already attempting to fix this with the open draft PR, bear with me! 😄

[enisdenjo]

🎉 This issue has been resolved in version 4.2.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[enisdenjo]

Just a short update, the referenced PR solves the 'close' listener warnings. However, we do create 'message' listeners on subscribe too - I guess they would raise the same warning.

So, as soon as I get rid of the 'message' listener - I'll merge the PR and effectively get rid of all potential MaxListenersExceededWarning warnings.

P.S. The reason why v4.1.1 raised no warnings for you, even though the 'message' listeners stayed exactly the same, is because your tests showcase single-result queries. As soon as you run the same example, but with streaming operations, a second warning would be raised pointing to the 'message' listeners.