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

eo-components

v0.0.19-rc.1

Published

Todo:

Downloads

5

Readme

Example

Todo:

  • We should deploy storybook on webdev

Development

This library uses npm, and not yarn, so please use npm!

To start storybook, run the following in the terminal npm run storybook. Note that this does not build the library. To build the library you can run npm run build or npm run start, the difference is that npm run start will build on file changes.

Adding packages

We should use as little external packages as possible, but if we need to add a package please add it to dependencies . Packages like prettier, eslint and typescript for example should be added to devDependecies.

If adding a package to peerDependecies please make sure it deserves to be there. One can read more at the following link Understanding the npm dependency model. In short, if react and react-dom are peerDependecies, then the project/application must have react and react-dom in its package.json. Packages in peerDependecies will not be installed by the library, but should be installed by the application/project that consumes this library.

Bundling

This project uses rollup for bundling. Rollup should treat external packages as external, and not bundle them with our library.
This is achieved by the following in rollup.config.js

`external: [...Object.keys(pkg.dependencies || {}), ...Object.keys(pkg.peerDependencies || {})],`

Deployment

Currently we are not publishing to npm, and are using gitlab with the use of tags. For this reason it is important to run npm run build before committing.