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

thr0w-api

v0.1.0

Published

Provides the Thr0w (Node.js) API.

Readme

README v0.0.2 / 29 APRIL 2016

Thr0w API

Introduction

The Thr0w Project is about building inexpensive and manageable interactive (or not) video walls using commodity hardware, web technologies, and open source software. The key to this solution is having one computer behind each screen networked to a single computer acting as a server. With this design, the splitting and synchronization of content is accomplished through software.

This repository provides the project's Thr0w (Node.js) API for the project's required Thr0w Server implementation available at:

https://github.com/larkintuckerllc/thr0w-server

Installation

npm install thr0w-api

Usage

The Thr0w (Node.js) API is closely aligned to the Thr0w (Client) API; so much so that one simply needs to understand it to use this API.

https://github.com/larkintuckerllc/thr0w-client

note: The one exception is that the client setBase method uses an URI while the Node.js setBase method uses a hostname.

The examples provided in ROOT/examples provide inline documentation on using the API.

The API reference is available at:

http://rawgit.com/larkintuckerllc/thr0w-api/master/doc/index.html

Contributing

Submit bug or enhancement requests using the Github Issues feature. Submit bug fixes or enhancements as pull requests. Specifically, follow GitHub's document Contributing to Open Source on GitHub.

https://guides.github.com/activities/contributing-to-open-source/

The JavaScript is to pass JSHint with the default configuration (with the node environment). The JavaScript is to pass JSCS with the Google preset.

The JavaScript is to comply with the following style guide.

  • Use named functions instead of passing an anonymous function in as a callback.
  • Define functions in the scope where they are used.
  • Place functions declarations at the end of the scope; rely on hoisting.

The exposed JavaScript classes (or objects) are to be documented using YUIDoc.

http://yui.github.io/yuidoc/

Credits

TODO

Contact

General questions and comments can be directed to mailto:[email protected].

License

This project is licensed under GNU General Public License.