Self-signed certs about websocket-as-promised HOT 3 CLOSED

Resolved - Had to use ws instead of websockets. Then as ws wouldn't work I had to implement the fix from #15 (comment)

Doesnt look like my msgs are making it to the server though, could this be another issue with using ws? When I follow the change you recommended in the previous thread, appending .ws to wsp it forces the connection closed without me calling a wsp.close(), when this occurs the connections closed event is 1006.

wsp.onClose.addListener(event => console.log(`Connections closed: ${event}`));
wsp.open()
  .then(() => wsp.onMessage.addListener(message => console.log('test: ' + message)))
  .then(() => wsp.ws.send('hello from client'))
  //.then(() => wsp.close())
  .catch(e => console.error(e));

from websocket-as-promised.

@narsariusv
Does the connection closed only when used with websocket-as-promised?

from websocket-as-promised.

Working with ws package is now officially supported (since 0.10.0).
Please have a look on this section in readme.

from websocket-as-promised.