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

c2fo-ui-guide

v0.1.0

Published

Code for creating frontend user interfaces.

Readme

ui-guide

Code for creating frontend user interfaces.

Usage

Currently this code is not ready on its own. We need to do more work to fully build out all the parts we need to build our interfaces.

Each of the pages found at the documentation site should show how and when to use various parts of the ui-guide.

Development

Prerequisites

Setup

In order to develop within the ui-guide you'll need to run the below commands. They install then node dependencies as well as the needed libraries to run jekyll.

  1. npm install
  2. grunt setup

Running

After you're initially setup all you need to have two windows open to run the site and get updates:

  1. grunt monitor
  2. jekyll serve

This does a few things:

  • Runs the jekyll site
  • Updates the output CSS as you work
  • Updates the pages so you do not need to restart the server

The local site can be see at http://localhost:4000/ui-guide.

Code Style

The current guide used for code development:

  1. Follow BEM for CSS naming
  • less variables do not follow BEM, they are not CSS
  • Naming should allows be block => element => modifier (e.g. person__hand--left-hand)
  1. The index.less file combines all less files together
  2. The mixins directory is only for true mixins
  3. Follow the http://cssguidelin.es/ when writing code, see existing code for examples
  4. Always add at least one example of your change to the example pages
  5. Make your contribution work for RTL styles

TODO

Overall project things to do are in a gist that can be found here:

https://gist.github.com/garrypolley/5c8d29df98cd3c1261cd

Things to cleanup as this project grows:

  • Add consumer docs for existing parts
    • Grid
    • #site-container
  • Add developer docs (code docs may be good enough when used with the consumer docs)
  • Add sub navigation for pages like typography and colors
  • Automate the gh-pages bits when making the development site legit