wrtc
Advanced tools
Readme
The best way to get started is to read through the Getting Started and Example sections before having a look through the open issues. Some of the issues are marked as good first bug, but feel free to contribute to any of the issues there, or open a new one if the thing you want to work on isn't there yet.
Once you've done some hacking and you'd like to have your work merged, you'll need to make a pull request. If your patch includes code, make sure to check that all the unit tests pass, including any new tests you wrote. Finally, make sure you add yourself to the AUTHORS file.
To install prerequisites with the apt-get package manager,
apt-get install python2.7 git-all pkg-config libncurses5-dev libssl-dev libnss3-dev libexpat-dev
To install prerequisites with the yum package manager,
yum install python git pkgconfig openssl-devel ncurses-devel nss-devel expat-devel
To install prerequisites using the homebrew package manager,
brew update
brew install git openssl pkg-config openssl ncurses nss expat
Some of these libraries may be installed by default. Package names for these libraries may differ between distributions.
The easiest way to install is via npm:
npm install wrtc
If you want to work from source:
git clone https://github.com/js-platform/node-webrtc.git
cd node-webrtc
npm install
Add a symlink to libncurses:
sudo ln -s /usr/lib/libncurses.so.5 /usr/lib/libtinfo.so.5
This is most common on Arch Linux. Set python2 as the default for npm:
npm config set python python2
Follow the instructions here: https://github.com/joyent/node/wiki/installing-node.js-via-package-manager
Once everything is built, try npm test as a sanity check.
You can run the data channel demo by node examples/bridge.js and browsing to examples/peer.html in chrome --enable-data-channels.
usage:
node examples/bridge.js [-h <host>] [-p <port>] [-ws <ws port>]
options:
-h host IP for the webserver that will serve the static files (default 127.0.0.1)
-p host port for the webserver that will serve the static files (default 8080)
-ws port of the Web Socket server (default 9001)
If the bridge and peer are on different machines, you can pass the bridge address to the peer by:
http://<webserver>/peer.html?<sockertserver:port>
By default the bridge will be the same IP as the webserver and will listen on port 9001.
The ping-pong example creates two peer connections and sends some data between them.
usage:
node examples/ping-pong-test.js
FAQs
Standards-compliant WebRTC implementation for Node
The npm package wrtc receives a total of 7,562 weekly downloads. As such, wrtc popularity was classified as popular.
We found that wrtc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.
Security News
The NVD is facing a significant backlog with over 12,500 CVEs awaiting analysis, and more than 50% of known exploited vulnerabilities (KEVs) left unenriched since mid-February.
Security News
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.