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

obby-components

v0.3.0

Published

Obby components library with storybook

Readme

Obby Components

Setup

nvm use 10.12.00
yarn
yarn link
# make sure you have obby lib linked first
yarn link obby-lib
# go to the app
npm link obby-components

Dev

cd src
mkdir <ComponentName>
cd <ComponentName>
touch <ComponentName>.js
touch <component-name>.less
touch stories.js
# export component in src/index.js
yarn run storybook

Deploy

yarn build
npm publish

Development convetions

  • Folder per component
  • Components names start with a capital
  • Each component is exported seperately in /src/index.js
  • We use the stories.js the components folder to build and test it
  • Include all relevant permutations of a component in its stories file so it is clear what it can do.
  • all less variables go in /styles/variables and any extra configuration files should go in /styles