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

components-library-demo-cesar

v1.0.1

Published

A components library

Readme

Demo component library

First time setup

  1. Use only npm for running scripts, in order to avoid some unexpected conflicts with different .lock files;
  2. Run npm i command to install project dependencies;
  3. Run npm run start to start Storybook and review components.

Publishing

Note: before publishing packages, you must have npm account and setup organization in order to publish scoped packages.

  1. Build components by running npm run build:components command;
  2. Publish components by running npm run publish:components command.

Development

  • Create new component under src directory;
  • Every component must have src directory with all of the source code. Include index.js file in order to avoid specific file path import declaration;
  • Each component must include package.json file, and should include .npmignore, CHANGELOG.md, LICENCE, README.md files;
  • When using imports from other components use their package.json name and include that name and specific path to aliases under /configs/aliases.config.js;
  • In order to check if published component works, add dependency to root package.json file, run npm i command and comment specific alias. Run storybook and test it.