ws

Sorry @victorperin, but I had to remove all timeout functionality because if the message is queued, it may cause the timeout for the confirmation event to expire even though the message has yet to be sent.

I did however replace the resolveOnEvent with p-event that supports timeouts. I am think

This is the error that I get when importing isomorphic-ws and bundling with rollup:

[!] Error: 'default' is not exported by node_modules/isomorphic-ws/browser.js, imported by node_modules/@holochain/conductor-api/lib.es/websocket/client.js
https://rollupjs.org/guide/en/#error-name-is-not-exported-by-module
node_modules/@holochain/conductor-api/lib.es/websocket/client.js (10:7)
 8:  

Hi and thanks for this library, it really ease things up.

I have detected that when you use WebSocketServer and go and try to establish an HTTP connection to the websocket port the server crashes and closes.

While I obviously don't expect the WS server to work properly when being contacted by the wrong protocol it should fail silently, or at least, allow the programmer to specify an error ca

• Located in popup.html and popup.js

There are currently 2 enums files:

• ./client/src/models/Enums.ts
• ./server/Enums.ts

both are very similar. Let's create only one, with all enums at [./