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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@saralaffin/project-5

v0.1.0

Published

Project 5 in General Assembly SEI35. Given 1.5 class days and a weekend to work on it.

Readme

Component Library

Project 5 in General Assembly SEI35. Given 1.5 class days and a weekend to work on it.

To see my components in Storybook, click here.

Technologies Used

CSS, Javascript, React, JSX, and Storybook

Approach Taken

Wrote out all componenets and potential CSS classes needed. Added more classes along the way.

Would have done differently/challenges

  • When sketching out components, should have psuedo coded what each component might look like
  • Conditionals and classes were hard to keep track of
  • I copied over my Button directory and ran into formatting bugs from the same class showing up in 2 different CSS files.
  • I tried a few different methods for conditional rendering, which makes the code hard to go back and edit.

Unsolved Problems

  • Clean up formatting on text input with button
  • Clean up Javascript/React code for readability

Authors

Mainly written by Sara Laffin. Help with CSS from my peers and various websites.

Requirements (Given by General Assembly)

You should build out a component library using React and Storybook. Your component library should be deployed tto GitHub Pages, Netlify, or Surge and published to the NPM Package registry.

Your component library should include all of the components in bouncer.xd mockqup from this Adobe XD mock-up folder.

Technical Requirements

Your project should meet the following requirements:

  • Runs without errors
  • Include the required components in the Adobe XD Mock-up
  • Be deployed to GitHub Pages, Netlify, or Surge
  • Be published to the NPM Package Registry
  • Includes a README written in well formatted Markdown (hint: look up a README template)
  • Shows a good commit history with frequent commits. We're looking for lots of small commits.

This project was created with Create React App. A component library was built out and deployed/visualized with Storybook.