rtc-io/faq

local development server that aims to make using browserify fast and fun

browser-side require() the node way

Cherry pickable JS functions

A small, simple, and fast DOM creation utility

cross-browser getUserMedia shim with node.js style error-first API.

Recursively mkdir, like `mkdir -p`

writable stream that concatenates strings or binary data and calls a callback with the result

cross-browser way to attach a media stream to a video element.

detect and launch browser versions, headlessly or otherwise

Functional thinking inspired DOM helpers (browserify and selective require friendly)

Option parsing for Node, supporting types, shorthands, etc. Used by npm.

Get free, randomized STUN and TURN servers for your WebRTC application

Cross browser getUserMedia implementation with support for rtc.io plugins

Create a WebRTC connection in record time

Common UI interaction patterns for working with rtc.io modules

Collision-resistant ids optimized for horizontal scaling and performance. For node and browsers.

Screenshare please - stat! Will make use of both command-line permissioned APIs and extensions to provide screensharing

Flow control the super easy way

Attach a media stream to an existing or new media element (basically attachMediaStream with support for rtc.io plugins)