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 🙏

© 2026 – Pkg Stats / Ryan Hefner

test-package-uvn-two

v4.6.5

Published

Core js library for video playback

Downloads

19

Readme

FMG-Video-SDK

Core js library for video playback

Building

To start developing you need to set up few things first:

$ npm install -g gulp-cli # In case you don't have it already
$ npm instal

Once that's done, you simply run: npm run serve for development or npm run serve:dist to serve the page from the distribution files. After serving, you simply need to start adding/modifying files, and browsersync will do its magic.

Testing

We are using Karma and Jasmine for unit testing, in order to get it up and running you should install:

$ npm install -g karma-cli phantomjs

Then you simply run $ gulp test

Versioning

SDK will be semantic versioned, using npm built-in scripts.

Patch release: Bug fixes and other minor changes -> will turn it into 1.0.1

npm version patch -m "Patch release version to %s"

Minor release: New features which don't break existing features -> will turn it into 1.1.0

npm version minor -m "Minor release version to %s"

Major release: Changes which break backwards compatibility, or implement something that is a big new feature-> will turn it into 2.0.0

npm version major -m "Major release version to %s"

This will create a new commit with the corresponding message

Distribution

We can run either npm run build or npm run serve:dist in order to generate/update the dist dir.

Logging

Logging level is set in the init function by sending a loglevel param:

FMG.init({ .. loglevel: 'verbose' .. });

SDK handles three levels of logging:

  • Production: Defined by prod value, and is set by default is non is sent. It will only print important errors.
  • Debug: Defined by debug value. Will print important errors and warnings.
  • Verbose: Degined by verbose value. Will print all kind of debugging messages. Including logs, warnings and errors.