feat: websocket-streams to ws

[YoDaMa]

No description provided.

[YoDaMa]

the errors I'm seeing on Node version 10 are not consistent and are on functionality not related to streams, so I'm going to consider this passing. The flakiness of tests still needs to be improved...

[fartagaintuxedo]

After this fix in v4.2 we are getting Uncaught (in promise) Error: ws does not work in the browser. Browser clients must use the native WebSocket object in all our applications.

[YoDaMa]

This bug is being tracked. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: fartagaintuxedo <[email protected]> Sent: Thursday, August 13, 2020 2:56:41 AM To: mqttjs/MQTT.js <[email protected]> Cc: Yoseph Maguire <[email protected]>; State change <[email protected]> Subject: Re: [mqttjs/MQTT.js] feat: websocket-streams to ws (#1108) After this fix in v4.2 we are getting Uncaught (in promise) Error: ws does not work in the browser. Browser clients must use the native WebSocket object in all our applications. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmqttjs%2FMQTT.js%2Fpull%2F1108%23issuecomment-673383555&data=02%7C01%7Cyoseph.maguire%40microsoft.com%7Cb7c21d7bfd6e4908a22d08d83f6f2e59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637329094035004444&sdata=oCHGepdVZ%2B5GYE8pysDQcdQ6bczz9%2FFOTf263BVyvBA%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6VMLC72R2BL7OFS2CBLYTSAO2FTANCNFSM4NOM44WA&data=02%7C01%7Cyoseph.maguire%40microsoft.com%7Cb7c21d7bfd6e4908a22d08d83f6f2e59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637329094035004444&sdata=0g9LOBOG9M42opVaOn0j%2BMhXaRkJt98mRNoaM%2F17MM4%3D&reserved=0>.