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

cs188-spring2022

v0.0.888

Published

A node module built by the best Drake class there ever was

Downloads

45

Readme

module-building

Documentation Assignment

testing for node module

Use "npm run test" to test all of the modules.

how to install

Use "npm install" to install any modules or code needed. Also use "npm rin lint" to see any given syntax isues. Then run "npm run lint -- --fix" to fix them.

functionality

issue #1 is used to find a valid string name that is under 100 characters. issue #2 is used to make sure the input state abreviation is valid. issue #3 compares three numbers, the max, min, and valToTest. It makes sure they are all valid numbers and that valToTest is between the min and max. issue #4 uses the above issues 1-3 to make sure that the input of a person is valid.