npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@istreamplanet/myriapod.js

v1.0.2

Published

Myriapod JavaScript Client

Downloads

7

Readme

Myriapod Javascript Client

Javascript client for playing back Myriapod streams. The following complete example shows how easy it is to use:

<html>
  <head>
    <!-- Include transpiled myriapod.js somehow, e.g. via webpack -->
    <script src="myriapod.min.js"></script>
  </head>
  <body>
    <video id="vid" autoplay></video>

    <script>
      // Get the video element from above.
      var video = document.querySelector('#vid');

      // Create a Myriapod instance for a given video ID and set up handlers.
      var myriapod = new Myriapod(video, 'SERVER:PORT/video/ID', {
        additional: 'server preflight data'
      });

      myriapod.on('error', function(err) {
        // Print any errors to the Javascript console for debugging.
        console.log(err);
      });
    </script>
  </body>
</html>

Architecture

The client creates a persistent WebSocket connection to the backend. If the connection is successful it waits for control messages and media data blobs. Control messages tell it how to create media source elements which are used to feed the data blobs into the associated HTML <video> element.

New dynamic media source URLs are created as needed when streams change or are restarted. These URLs should be set on the video element like in the example above.

            /- Text control messages -> Create media source
WebSocket -<
            \- Binary blob messages -> Load into media source (buffer)

Clients will automatically reconnect when the WebSocket connection is lost.

Usage

npm install --save @istreamplanet/myriapod.js

Running tests

To run tests, execute the following command:

$ npm test

Reference

Constructor

Myriapod([video], [url], [preflightMetadata])

Create a new Myriapod instance. Takes an optional HTML video element, optional playback URL without the protocol and optional data to send to the server when the connection is first opened.

// Get the video element:
const video = document.querySelector('#my-video');
const url = 'host:port/video/id';
const preflightMetadata = {
  identity: 'identity',
  token: 'token'
};

// Create and play back a stream:
let mp = new Myriapod(video, url, preflightMetadata);

// Create but call `play` separately. It is safe to call `play`
// multiple times:
mp = new Myriapod(video, null, preflightMetadata);
mp.play(url, preflightMetadata);

// Or, manage everything yourself if you want:
mp = new Myriapod();
mp.on('source', src => {
  video.src = src;
})
mp.on('buffer-updated', (source, buffer, start, end) => {
  // Seek into the buffer if playback falls behind.
  if (video.currentTime < start) {
    video.currentTime = start
  }
})
mp.on('error', err => {
  console.log(err);
  mp.destroy();
  mp = null;
})
video.addEventListener('canplay', () => {
  video.play();
})

Instance Properties

myriapod.source

The MediaSource for the current stream.

myriapod.buffer

The SourceBuffer attached to the MediaSource above.

myriapod.ws

The WebSocket connection to the server that is used to read control messages and video stream data.

Instance Methods

myriapod.on(name, handler)

Register a new event handler.

myriapod.on('error', err => {
  console.log(`Error playing back! ${err}`);
})

myriapod.play(url, preflightMetadata)

Start playback of a new video URL (without the protocol).

myriapod.play('host:port/video/id', {token: 'token'});

myriapod.destroy()

Destroy and clean up the player. It is not safe to use the instance after destroy has been called.

myriapod.destroy();

Events

The following events are available for attaching a listener:

Event | Arguments | Description ----- | --------- | ----------- buffer-updated | source, buffer, start, end | The media source buffer has been updated. error | err | An error occurred. destroyed | n/a | Myriapod instance has cleaned up and is ready to be garbage collected. source | source | A new source is ready and can be attached to an HTML <video> element's src attribute.