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

knit-hutchida

v1.0.56

Published

This is an example of how to develop a component library using Storybook and publishing to NPM.

Readme

Component Library example using Storybook

This is an example of how to develop a component library using Storybook and publishing to NPM.

Initial Setup

npm install

Run Storybook

npm run storybook

Go ahead and create new react components, make changes to existing components, and check how they look using Storybook. When ready, go ahead and publish to npm.

Login to npm

If you're not already logged in to npm through the command line, run the below command:

npm login

You should only need to login once. If you don't yet have a NPM account go to www.npmjs.com to create one first.

Publish to npm

In order to publish your component library to npm the version number in the package.json needs to be incremented, else you will receive an error. When the version number is unique, go ahead and run

npm publish

What next?

Now in your UI codebase you can reference the package you created on NPM as a dependency. You should reference the package version you wish to install (probably the latest one in most cases) to see the latest changes to the library in your UI. See the example knit-ui repo for more information.