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

pair14js

v0.0.3

Published

Pair14JS is set of UI components

Readme

Team Pair a' Dice

Web Component Repository

Build Status

Team Members

  1. Stephanie Mitchener - Lead
  2. Haozhi(Flik) Hu - Co-lead
  3. Mingxun(Tyler) Song - Quality Assurance
  4. Dung(Devon) Do - DevOps
  5. Haimei Yang - DevOps
  6. Eldon K. Y. Tay - Tool & Utility
  7. Kent Thai - Coder
  8. Alex Kurland - Coder
  9. Axel Drozdzynski - Coder

Getting Started

  1. Install Node.js
  2. Download from the master branch
  3. Open the directory and install dependencies
    • npm install

The Demo

  1. Navigate to the demo/ folder
  2. Run any of the demo HTML files in your favorite browser

The Web Components

  1. We have core-hello, pair-switch, pair-slider, pair-button, core-color-picker, and more to come
  2. All of the web component are located in lib/elements/
  3. Access the individual JavaScript classes within the web component folders

Unit Testing

  1. All Unit Tests are created with Jasmine, a JavaScript testing framework
  2. They are all located in test/unit-test/
  3. Access the individual Javascript unit tests within the web component folders
  4. Run all unit tests:
    • ./node_modules/karma/bin/karma start --single-run
  5. To update the existing test
  6. To add a new test file
    • include a new folder in test/unit-test/
    • add a testing file within the new folder

Browser Testing

  1. All browser tests are created with TestCafe, an end-to-end testing framework
  2. They are all located in test/browser-test
  3. Access the individual Javascript unit tests within the web component folders
  4. Run individual browser test:
    • ./node_modules/.bin/testcafe chrome,firefox ./test/browser-test/ + web-component-folder/browser-test-file
    • To run locally, you will need to download the executable from the browsers you want to test on.
  5. To update the existing test
  6. To add a new test file,
    • include a new folder in test/browser-test/
    • add a testing file within the new folder

Travis CI

  1. To run Travis CI, push your changes to GitHub on any of the branches
  2. Open our Travis CI Build
  3. If you added a new browser test
    • navigate to .travis.yml file
    • under scripts, include the command for running individual browser tests

Code Climate

  1. To run Code Climate, push your changes to GitHub on any of the branches
  2. If your build passes all of the tests on Travis CI, a snapshot of your code will be analyzed by Code Climate
  3. Open our Code Climate Build

JSDoc

  1. To be completed