opentok-react

TLDR

This is a forked version of the original opentok-react package with some security fixes.

Disclaimer

This version has been published to allow the use of patches to security holes in the original opentok-react package while waiting for the original package to merge in the PR fixes that we submitted.

I would recommend using the original opentok-react package as this forked version of the package may or may not be updated depending on the need. If you also want to use opentok-react but wish to patch the current security holes then by all means use this version as is.

React components for OpenTok.js

Contents

• opentok-react
  • TLDR
  • Disclaimer
  • Contents
  • Pre-Requisites
  • Install
  • Example App
  • Usage
    • Importing opentok-react
    • Example with OTSession Component
    • Example with createSession Helper
  • API Reference
    • OTSession Component
    • OTPublisher Component
    • OTStreams Component
    • OTSubscriber Component
    • createSession Helper
    • preloadScript Higher-Order Component
  • Custom Build
  • Contributing
  • Tests
  • About

Pre-Requisites

1. NodeJS
2. Register a TokBox account: https://tokbox.com/account/user/signup

Install

Add opentok-react as a dependency of your application:

yarn add opentok-react

Or if you're still using npm:

npm install --save opentok-react

Then include opentok.js before your application:

<script src="https://static.opentok.com/v2/js/opentok.min.js"></script>

Alternatively, wrap your top-level component using OpenTok with the preloadScript HOC. The HOC will take care of loading opentok.js for you before rendering.

Example App

There is an example application provided in example/ and you can run it with the following steps:

1. git clone https://github.com/opentok/opentok-react.git
2. cd opentok-react/example/
3. cp config.template.js config.js
4. Edit config.js:
5. Add your OpenTok API key, Session ID and Token (https://tokbox.com/account/)
6. Add your Chrome Extension ID (https://tokbox.com/developer/guides/screen-sharing/js/)
7. cd ..
8. yarn (or npm install)
9. npm run example
10. Visit http://localhost:8000 in your browser

Refer to the App.js, Publisher.js and Subscriber.js files in example/components/ for library usage.

Usage

The following sections explains how to import and use opentok-react in your React application.

Importing opentok-react

Import the opentok-react components into your React application:

import { OTSession, OTPublisher, OTStreams, OTSubscriber } from 'opentok-react';

Or require it if you need to use CommonJS modules:

const { OTSession, OTPublisher, OTStreams, OTSubscriber } = require('opentok-react');

Example with OTSession Component

class MyApp extends React.Component {
  render() {
    return (
      <OTSession apiKey="your-api-key" sessionId="your-session-id" token="your-session-token">
        <OTPublisher />
        <OTStreams>
          <OTSubscriber />
        </OTStreams>
      </OTSession>
    );
  }
}

Example with createSession Helper

class MyApp extends React.Component {
  constructor(props) {
    super(props);
    this.state = { streams: [] };
  }

  componentWillMount() {
    this.sessionHelper = createSession({
      apiKey: 'your-api-key',
      sessionId: 'your-session-id',
      token: 'your-session-token',
      onStreamsUpdated: streams => { this.setState({ streams }); }
    });
  }

  componentWillUnmount() {
    this.sessionHelper.disconnect();
  }

  render() {
    return (
      <div>
        <OTPublisher session={this.sessionHelper.session} />

        {this.state.streams.map(stream => {
          return (
            <OTSubscriber
              key={stream.id}
              session={this.sessionHelper.session}
              stream={stream}
            />
          );
        })}
      </div>
    );
  }
}

API Reference

The opentok-react library comprises of:

• OTSession Component
• OTPublisher Component
• OTStreams Component
• OTSubscriber Component
• createSession Helper
• preloadScript Higher-Order Component

OTSession Component

| Prop | Type | Required | Description | | --- | --- | --- | --- | | apiKey | String | Yes | TokBox API Key | sessionId | String | Yes | TokBox Session ID | token | String | Yes | TokBox token | eventHandlers | Object<Function> | No | Event handlers passed into session.on | onConnect | Function() | No | Invoked when session.connect successfully completes | onError | Function(err) | No | Invoked when session.connect fails

The OTSession component manages the connection to an OpenTok Session. It passes the Session instance as the session prop to its child components. It is recommended that you nest OTPublisher and OTStreams inside OTSession:

<OTSession apiKey="your-api-key" sessionId="your-session-id" token="your-session-token">
  <OTPublisher />
  <OTStreams>
    <OTSubscriber />
  </OTStreams>
</OTSession>

OTPublisher Component

| Prop | Type | Required | Description | | --- | --- | --- | --- | | session | Session | No | OpenTok Session instance. This is auto populated by wrapping OTPublisher with OTSession | properties | Object | No | Properties passed into OT.initPublisher | eventHandlers | Object<Function> | No | Event handlers passed into publisher.on | onInit | Function() | No | Invoked when OT.initPublisher successfully completes | onPublish | Function() | No | Invoked when session.publish successfully completes | onError | Function(err) | No | Invoked when either OT.initPublisher or session.publish fail

The OTPublisher component will initialise a publisher and publish to a specified session upon mounting. It will also ensure the Publisher video element is attached to the DOM inside the component rather than appending to the body (which is the Publisher's default behaviour).

<OTSession apiKey="your-api-key" sessionId="your-session-id" token="your-session-token">
  <OTPublisher />
</OTSession>

If you are not using OTSession then you must specify a Session object using the session prop.

<OTPublisher session={this.sessionHelper.session} />

Use the properties prop to specify a properties object for OT.initPublisher and the eventHandlers prop to specify an object of event handlers for Publisher#on.

class MyApp extends React.Component {
  constructor(props) {
    super(props);

    this.publisherProperties = {
      audioFallbackEnabled: false,
      showControls: false
    };

    this.publisherEventHandlers = {
      streamCreated: event => {
        console.log('Publisher stream created!');
      },
      streamDestroyed: event => {
        console.log('Publisher stream destroyed!');
      }
    };
  }

  render() {
    return (
      <OTSession apiKey="your-api-key" sessionId="your-session-id" token="your-session-token">
        <OTPublisher
          properties={this.publisherProperties}
          eventHandlers={this.publisherEventHandlers}
        />
      </OTSession>
    );
  }
}

The properties prop is used for initial set up of the Publisher and making changes to it will not update the Publisher, you will instead need to invoke Publisher methods. To facilitate this the Publisher instance is exposed via the getPublisher() component method. You should always call this method to get the latest Publisher instance instead of keeping a reference to it as it's possible for the Publisher instance to change, leaving you with a stale reference.

However, for convenience the OTPublisher does watch for changes on a few keys of the properties object and makes the necessary changes. Currently these are:

| Publisher Property | Action | | --- | --- | | videoSource | Destroys and recreates the Publisher with the new video source. This is the only way to change the video source of a Publisher. This is used in the example application to allow the user to toggle between publishing their camera and publishing their screen | | publishAudio | Calls publisher.publishAudio() to toggle audio on and off | | publishVideo | Calls publisher.publishVideo() to toggle video on and off |

There are plans to support more Publisher properties but for now you will have to call getPublisher() to retrieve the Publisher instance and make the necessary changes yourself.

OTStreams Component

| Prop | Type | Required | Description | | --- | --- | --- | --- | | children | ReactElement | Yes | Must have a single child component that accepts session and stream props, eg. OTSubscriber | session | Session | Yes | OpenTok Session instance. This is auto populated by wrapping OTStreams with OTSession | streams | Array<Stream> | No | Array of OpenTok Stream instances. This is auto populated by wrapping OTStreams with OTSession

OTSubscriber Component

| Prop | Type | Required | Description | | --- | --- | --- | --- | | session | Session | No | OpenTok Session instance. This is auto populated by wrapping OTSubscriber with OTStreams | stream | Stream | No | OpenTok Stream instance. This is auto populated by wrapping OTSubscriber with OTStreams | properties | Object | No | Properties passed into session.subscribe | eventHandlers | Object<Function> | No | Event handlers passed into subscriber.on | onSubscribe | Function() | No | Invoked when session.subscribe successfully completes | onError | Function(err) | No | Invoked when session.subscribe fails

The OTSubscriber component will subscribe to a specified stream from a specified session upon mounting. It will also ensure the Subscriber video element is attached to the DOM inside the component rather than appending to the body (which is the Subscriber's default behaviour).

<OTStreams>
  <OTSubscriber />
</OTStreams>

If you are not using OTStreams then you must provide a Stream object using the stream prop and a Session object using the session prop.

{this.sessionHelper.streams.map(stream => (
  <OTSubscriber
    key={stream.id}
    session={this.sessionHelper.session}
    stream={stream}
  />
))}

Use the properties prop to specify a properties object for session.subscribe and the eventHandlers prop to specify an object of event handlers for Subscriber#on.

class MyApp extends React.Component {
  constructor(props) {
    super(props);

    this.subscriberProperties = {
      preferredFrameRate: 15,
      showControls: false
    };

    this.subscriberEventHandlers = {
      videoDisabled: event => {
        console.log('Subscriber video disabled!');
      },
      videoEnabled: event => {
        console.log('Subscriber video enabled!');
      }
    };
  }

  render() {
    return (
      <OTSession apiKey="your-api-key" sessionId="your-session-id" token="your-session-token">
        <OTStreams>
          <OTSubscriber
            properties={this.subscriberProperties}
            eventHandlers={this.subscriberEventHandlers}
          />
        </OTStreams>
      </OTSession>
    );
  }
}

The properties prop is used for initial set up of the Subscriber and making changes to it will not update the Subscriber, you will instead need to invoke Subscriber methods. To facilitate this the Subscriber instance is exposed via the getSubscriber() component method. You should always call this method to get the latest Subscriber instance instead of keeping a reference to it as it's possible for the Subscriber instance to change, leaving you with a stale reference.

However, for convenience the OTSubscriber does watch for changes on a few keys of the properties object and makes the necessary changes. Currently these are:

| Subscriber Property | Action | | --- | --- | | subscribeToAudio | Calls subscriber.subscribeToAudio() to toggle audio on and off | | subscribeToVideo | Calls subscriber.subscribeToVideo() to toggle video on and off |

There are plans to support more Subscriber properties but for now you will have to call getSubscriber() to retrieve the Subscriber instance and make the necessary changes yourself.

createSession Helper

The createSession helper has been provided to easily create a session and monitor the current list of subscriber streams.

class MyApp extends React.Component {
  componentWillMount() {
    this.sessionHelper = createSession({
      apiKey: 'your-api-key',
      sessionId: 'your-session-id',
      token: 'your-session-token',
      onStreamsUpdated: streams => {
        console.log('Current subscriber streams:', streams);
      }
    });
  }

  componentWillUnmount() {
    this.sessionHelper.disconnect();
  }
}

The createSession helper returns an object with the following properties:

• session - The Session instance.
• streams - An up-to-date array of Stream instances.
• disconnect - A clean up function. Call this when your component unmounts.

Use of this helper is optional and you can instead use the OTSession component or directly call OT.initSession and listen to streamCreated events if you prefer.

preloadScript Higher-Order Component

| Prop | Type | Required | Description | | --- | --- | --- | --- | | opentokClientUrl | String | No | The URL of the OpenTok client script to load. It defaults to https://static.opentok.com/v2/js/opentok.min.js. | loadingDelegate | ReactElement | No | An element that will be displayed while the OpenTok client script is loading. It defaults to an empty <div />.

In larger applications, one might not want to load the opentok.js client with a <script> tag all the time. The preloadScript higher-order component will do this for you at the appropriate time.

For example, imagine you have a React Router application with the following route structure:

<Router>
  <Route path="/">
    <IndexRoute component="..." />
    <Route path="something" component="..." />
    <Route path="video" component={VideoChat} />
    <Route path="something-else" component="..." />
  </Route>
</Router>

What you'd like to do is delay the loading of opentok.js until the VideoChat component is being used. Here's how you can do this:

class VideoChat extends React.Component {
  // All the code of your component
}

export default preloadScript(App);

Custom Build

1. git clone https://github.com/opentok/opentok-react.git
2. cd opentok-react/
3. yarn (or npm install)
4. Modify code in src/
5. npm run build
6. Check that files in dist/ have been updated.

Contributing

If you make changes to the project that you would like to contribute back then please follow the contributing guidelines. All contributions are greatly appreciated!

Tests

Run the unit tests locally with the following command:

npm run unit

By default this will launch the Chrome browser. To run tests in Firefox use:

npm run unit -- --browsers Firefox

Run the linter with:

npm run lint

The unit tests are automatically run on Travis on both Chrome and Firefox and the current build status is shown at the top of this document.

About

Originally authored by Aiham Hammami. Currently maintained by TokBox Inc..