npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




sort of like react but not trying to be as smart. Components and a global state.





Sort of like React but not trying to be as smart.




    <!-- you should probably bundle these files -->
    <script src='lib/ElemenTailor/elementailor.js'></script> <!-- for creating elements -->
    <script src='onestate.js'></script>
    <script src='inputComponent.js'></script>
    <script src='textComponent.js'></script>
    <script src='app.js'></script>
    <div id='root'></div>
    <div id='root1'></div>

writing components:

// inputComponent.js

let inputComponent = () => {
    // creating the element
    this.element = ElemenTailor.create('input', {
        'id': 'inputComponent',
        'type': 'text'

    this.onMount = () => {
        this.onTyped = this.onTyped.bind(this);

        this.element.addEventListener('keyup', this.onTyped);

    this.onTyped = (e) => {
        // change the current state, and bind it to this element id
        onestate.setState(, {'text': this.element.value});

// textComponent.js

let textComponent = () => {
    // creating the element
    this.element = ElemenTailor.create('div', {
        'class': 'textComponent',
        'id': 'textComponent'

    this.tick = () => {
        var text = onestate.getState()['inputComponent'].text;

        if (typeof text != 'undefined')
            this.element.innerHTML = text;

Intialization code:

// app.js

document.addEventListener('DOMContentLoaded', function(e) {

    onestate.instantiate(new inputComponent(), '#root'); // mounting
    onestate.instantiate(new textComponent(), '#root1'); // mounting