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

partnr-style-guide

v0.0.31

Published

Partnr's style for web components

Readme

Partnr Style Guide

This project was formed from a need to create and explicitly define individual Partnr UI components.

You can reuse any of thse components by running:

npm install partnr-style-guide

then in your Sass styles, using this:

@import /path/to/node_modules/src/partnr-style

or building the partnr-style.sass file explicitly and moving the resulting static file to a place where you can serve it directly.

##Development

To run this program, you'll need to run:

npm install

Then, once that has finished, run:

./node_modules/.bin/gulp serve

This will start a static server on port 9090. This will also listen to all changes in the src directory and build the relevant files. From there you can reload the browser to see your changes.

##Deployment

For now, we just use a (free tier) Heroku project hosted at style.partnr.org (which is an alias of partnr-style-guide.herokuapp.com)

If you want to emulate the heroku build process locally, then you should run:

ENV=production gulp build

and everything will build as if it were on the remote heroku server.

###NOTE: the only thing that's a real discrepancy between heroku and npm is that heroku requires all node_modules to be in dependencies and not devDependencies of the package.json.