Using this package in a browser client application (instead of from a Node.js application) does not seem to be sufficiently covered in the documentation.
does not work out-of-the-box because it requires RequireJS client-side. And getting reconnecting-websocket to work in combination with RequireJS isn't trivial, as even the troubleshooting section at http://requirejs.org/docs/errors.html#notloaded does not clearly provide solutions for getting it working.
I guess that a basic instruction "How/where to install reconnecting-websocket in your client-side web application directory structure" would help out greatly.
Using this package in a browser client application (instead of from a Node.js application) does not seem to be sufficiently covered in the documentation.
That is, the simple case
does not work out-of-the-box because it requires RequireJS client-side. And getting reconnecting-websocket to work in combination with RequireJS isn't trivial, as even the troubleshooting section at http://requirejs.org/docs/errors.html#notloaded does not clearly provide solutions for getting it working.
I guess that a basic instruction "How/where to install reconnecting-websocket in your client-side web application directory structure" would help out greatly.