Socket
Socket
Sign inDemoInstall

rtc-core

Package Overview
Dependencies
Maintainers
1
Versions
28
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

rtc-core - npm Package Compare versions

Comparing version 0.1.2 to 0.2.0

detect.js

4

package.json

@@ -7,3 +7,3 @@ {

],
"version": "0.1.2",
"version": "0.2.0",
"dependencies": {

@@ -19,3 +19,3 @@ "pull-stream": "~2.20.0",

"scripts": {
"gendocs": "cat index.js peer.js errorcodes.js | $(npm bin)/emu > README.md",
"gendocs": "cat index.js $(find *.js -not -path \"index.js\") | $(npm bin)/emu > README.md",
"test": "$(npm bin)/tape test/all.js"

@@ -22,0 +22,0 @@ },

@@ -6,2 +6,32 @@ # rtc-core

## rtc-core/detect
A browser detection helper for accessing prefix-free versions of the various
WebRTC types.
### Example Usage
If you wanted to get the native `RTCPeerConnection` prototype in any browser
you could do the following:
```js
var detect = require('rtc-core/detect'); // also available in rtc/detect
var RTCPeerConnection = detect('RTCPeerConnection');
```
This would provide whatever the browser prefixed version of the
RTCPeerConnection is available (`webkitRTCPeerConnection`,
`mozRTCPeerConnection`, etc).
## Core Error Codes
### HSIP
Handshake in Progress.
### REQCHAN
This error condition is encountered when a peer connection is used without
being assigned a valid signalling channel to start with.
## Peer prototype reference

@@ -33,12 +63,1 @@

### send(data)
## Core Error Codes
### HSIP
Handshake in Progress.
### REQCHAN
This error condition is encountered when a peer connection is used without
being assigned a valid signalling channel to start with.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc