Remove `ws` from browser builds
See original GitHub issueCurrently, when installing autobahn with npm for use in the browser (ie. angular2), you need to manually install bufferutil
and utf-8-validate
to fulfill unmet dependencies by ws
. Is there any reason why we can’t remove ws
from browser builds? I’m assuming it is only used in nodejs.
"browser": {
"lib/transport/rawsocket.js": false,
"ws": false
....
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to terminate a WebSocket connection?
According to the ws documentation, you need to call websocket.close() to terminate a connection.
Read more >ws: a Node.js WebSocket library - GitHub
Passes the quite extensive Autobahn test suite: server, client. Note: This module does not work in the browser. The client in the docs...
Read more >Building a Complete WebSocket App From Scratch ... - YouTube
Today you're gonna implement the Web Socket protocol from scratch using only Node.js and JavaScript. You'll get to know what are bitwise ...
Read more >WebSockets and Node.js - testing WS and SockJS by ...
Building a cursor position sharing web app to demonstrate how to implement WebSockets with Node.js, and the pros and cons of WS and...
Read more >WebSocket - Web APIs | MDN
desktop desktop
Chrome Edge
WebSocket Full support. Chrome4. Toggle history Full support. Edge12. Toggl...
WebSocket() constructor Full support. Chrome4. Toggle history Full support. Edge12. Toggl...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Could a pre-built browser version be published to npm?
That would allow folks to install from npm and use whatever build system they please without having to solve issues like this all over again.
Ok, I’ve managed to cut down browser version to 1/3 of original size (from 181KB to 58KB for the jgz):