The fix #89 for issue #86 was merged before a test was written to expose the issue. So, I think this repo would benefit from a test so that the issue doesn't reemerge in the future. Specifically, there should be a close test (similar to testServerClose) with a TLS enabled server using websocket-kit which communicates with a websocket-kit client.
The fix #89 for issue #86 was merged before a test was written to expose the issue. So, I think this repo would benefit from a test so that the issue doesn't reemerge in the future. Specifically, there should be a close test (similar to
testServerClose) with a TLS enabled server using websocket-kit which communicates with a websocket-kit client.