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 🙏

© 2025 – Pkg Stats / Ryan Hefner

liso

v1.0.0

Published

smooth testing

Readme

redpill

RedPill lets non-technical people peek under the hood of web apps.

Features

When the page loads we register:

  • Page URL
  • Client's Browser + Version
  • Client ViewPort (width/height of browser window)

Track/record actions performed on the page

  • Page scroll (top value)
  • Click/Touch events [x,y], element type and class/id

What happens to this data?

  • Save this data to local storage / cookie so user can track their own history.
  • Send data over WebSocket to server and broadcast to connected obeservers

Notes

  • Capybara cheat sheet: https://gist.github.com/zhengjia/428105

A simple client-side debug viewer.

I wrote this a while back. Its not very efficient, but it solved the problem I had at the time (keeping track of viewport width/height)

I've been debating weather to re-write it using a Library (e.g. JQuery or Zepto) but want to keep it lightweight.

How do I write this TDD/TFD...? Karma.js?

Notes

YUI has a Y.log('msg here') method which does something similar to what I want: http://yuilibrary.com/yui/docs/console/ but it requires loading the YUI library which is 90kb minified! :-(

instead I want to create a 2k file which then loads all the other components JIT only if the person using the app wants/needs them.

I want to allow people to opt-in to analytics and to have full access to their own stats. i.e. "personal analytics". But don't want to over-complicate it... Need to strike a balance between features and simplicity.

Considering using Require.js to load different elements... Which means I need to write a require.js tutorial... :-)