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

edenspiekermann-bright

v2.0.0

Published

easy to use brightcove facade

Downloads

1

Readme

bright

This facade wraps the brightcove smart player api with an easy to use interface.

Installation

Until the library is published on npm you can install it via the github url scheme.

npm install edenspiekermann-bright --save

Usage

The source files are built by webpack to the UMD format. This means you can require dist/bright.js via webpack, browserify or require.js. Although it’s not recommended you can also include dist/bright.min.js in your html. This creates a global variable called Bright.

Common.js (webpack, browserify…)

var Bright = require('bright'); // installed via npm
var Bright = require('./path_to/bright.js'); // use the one in the dist folder

var player = Bright(options);

Require.js

require(['Bright'], function(Bright) {
  var player = Bright(options);
});

Global Variable

<script src="//admin.brightcove.com/js/BrightcoveExperiences.js"></script>
<script src="bright.min.js"></script>
<script src="your_scripts.js">
// main.js
var player = Bright(options);

Note: //admin.brightcove.com/js/BrightcoveExperiences.js has to be loaded before bright.js. Use your favorite script loader or simply add a script tag before your main js file.

API

Example HTML:

<div id="player"></div>

The brightcove player will be appended as a child to this element.

var player = Bright({
  element: domElement, // [required] parent dom element of the video player
  video: videoId,      // [required] reference id ('ref:XXXXX') or video id (number)
  player: playerKey    // [required] playerKey of the brightcove player

  // append other brightcove options here (optional)
});

player.on('end', function(player) {
  player.load(videoId);
});

Possible options for brightcove can be found at this page from the official documentation.

Currently supported events:

  • load
  • play
  • pause
  • end

These event methods are copied from maxhoffmann/emitter:

  • on(event, fn)
  • once(event, fn)
  • off(event, fn)

Testing

Video and player id for testing are taken from brightcove’s example page. You may have to update them if they change.

Development

  1. Clone the repository
  2. npm install
  3. npm start to watch for file changes in src/bright.js
  4. make changes
  5. npm test starts a local server & opens your default browser with http://localhost:8000/tests
  6. npm run build if all tests pass
  7. push to develop, merge into master