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

quality-approach-example-library

v0.4.2

Published

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app). This is a components library based on Atomic Design approach.

Readme

Getting Started with Create React App

This project was bootstrapped with Create React App. This is a components library based on Atomic Design approach.

Important notice

This is an example about testing scope and strategy. This is not something we have to follow by the book. What it's important here is to better understand which type of tests we have to perform and when.

Mindset: All in one

Goal is to have an all in one approach:

  • Documentation
  • State preview
  • Tests

In a component folder, you should at least find this files:

  • *.mdx as a documentation, including usecases
  • *.usecases or *.stories to display state of components
  • *.test.js or *.steps.test.js file to tests usecases
  • *.js or *.jsx as code

Available Scripts

In the project directory, you can run:

yarn storybook

Runs storybook.
Open http://localhost:6006 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

yarn coverage

Launches the coverage report.
Open http://localhost:6007 to view it in your browser.

yarn test

Runs test in a watch mode and generate report

yarn test:ci

Runs tests as a CI and do not generate report

Pre-commit

Each time developers want to commit, yarn test:ci is exectued to ensure you cannot commit something not tested:

  • Should not have failed tests
  • Should reach coverageThreshold defined within package.json
"jest": {
    "testMatch": [
      "**/*.steps.test.js", // Include BDD
      "**/*.test.js" // Include TDD
    ],
    "collectCoverageFrom": [
      "src/components/**",
      "!src/**/*.stories.js",
      "!src/**/*.usecases.js"
    ],
    "coverageThreshold": {
      "global": {
        "branches": 60,
        "functions": 60,
        "lines": 60,
        "statements": 60
      }
    }
  }