This should not cause compile issues when simple-peer is not installed
(because client-side JS will be precompiled after pkg is published in
NPM repository) because types are not used in runtime.
The URL can be set by either:
1. Setting the `baseUrl` property in `config/default.json`,
`config/local.json`, or `config/${NODE_ENV}.json` file.
2. Setting the `PEERCALLS_BASE_URL` environment variable.
For example:
```
$ PEERCALLS_BASE_URL=/test1/test2 npm start
> peer-calls@2.0.3 start /peer-calls
> node src/index.js
peercalls WebSocket URL: /test1/test2/ws +0ms
peercalls Listening on: 3000 +76ms
```
In this case, opening `http://localhost:3000/test1/test2` would open the
homepage.
Fix#42
During the time of the initial release of Peer Calls, the server and
client sockets used to have different namespaces - one side had `/#`
prepended to the name, whereas the other did not, so I had to check for
this in the code.
This was fixed since the release of [SocketIO v1.5.0][1], thus breaking the
compatibility with PeerCalls. Any new `npm install` would break this
because of the way it works - it tries to install the latest available
"compatible" release.
As of this commit, the SocketIO version is locked to v1.6.0.
[1]: https://github.com/socketio/socket.io/releases/tag/1.5.0
