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

hackathon_cohort-component-library

v0.1.3

Published

A component library built in a day!

Readme

Cohort component library

A component library built in a day!

Building our components - morning

Each team will have one component to build. You must think about what your component should do and what props it will need. Decide what options to include, e.g. sizes, colors, other styles and modes. Think about what options you've seen in other UI component libraries for inspiration. Use Storybook for development and to document how your component can be used. Write tests to show your component works.

You'll be working with this repo directly rather than in classroom links, so please follow the instructions below carefully to avoid any conflicts with other teams!

Components and teams

  • Button (Example)
  • Dropdown menu (Team 1)
  • Checkbox (Team 2)
  • Toggle switch (Team 3)
  • Time picker (Team 4)
  • Range input (Team 5)
  • Number input (Team 6)
  • Star rating (Team 7)
  • Page header (Team 8)
  • Avatar image (Team 9)
  • List (Team 10)

Instructions

  • In the issues tab, find the issue that corresponds to your component. Assign each member of your team to this issue.

  • Branch off from this repo. Name your branch your component's name.

  • Once on your branch, make a new folder in src/components for your component. Only add/change files inside of this folder.

  • Design your component. Think about what props it should take and what options the user should have.

  • Use Storybook for local development and documentation.

  • Write tests to show that your component works.

  • Once you're finished, create a pull request against the main branch. If time, invite another team to review your code.

Using our components - afternoon

To view the components in Storybook, run npm run storybook.

To run the tests, run npm test.

Once the library is published, install it into another project using npm i soc-bc7-components.

Then you should be able to consume components by importing.

import { Button } from "soc-bc7-components";