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 🙏

© 2024 – Pkg Stats / Ryan Hefner

blackboxsa

v1.0.2

Published

Semantic Release System

Downloads

5

Readme

Getting Started with Story Book

This project was bootstrapped with Create React App and Story Book by the Black Box product team.

In the project directory, you can run the following:

npm install

This should install everything needed to run storybook, as well as all the dependencies needed for the components.

npm run storybook

This will start storybook, which should automatically open your browser to: http://localhost:6006

The page will reload if you make edits.
You will also see any lint errors in the console.

Work Flows

Currently the repo is setup to GitHub Actions, which automatically publishes the development branch to Chromatic at this URL. Chromatic tests are run whenever any code is pushed or merged into the development branch. Once merged, the release action is run, and if all tests are passed, the code is published to the npm package. NB, you need to add a label to the PR request for the release action to work.

Building a component

Make sure to adhere to the following checklist:

  • Default props are declared
  • Proptypes are declared
  • SCSS file sits with js component and uses sass variables from variables.scss where possible
  • Component is presentational and doesn't contain logic, but can receive logic through correct props
  • All dependencies are noted in the storybook component documentation
  • Correct SB controls are put in place for design team to interact with component

Creating a pull request

  • Add a label to your pull request documentation, feature or bug
  • Request a code review
  • Merge in the code
  • Log in to your chromatic account and accept the changes / or ask a designer to accept them
  • Check to see that your update has reflected on Chromatic
  • Check to see that your update has reflected in the npm library
  • Test it by pulling it into another project to see it reflects