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

@alabebop/how-to-npm

v1.0.1

Published

Test npm project

Readme

Learn to npm!

This repository contains my learning notes of the NodeSchool workshop "How to npm"

  • If you get a .lock error trying to install a package, it may be caused by your previous installing packages in your home folder with sudo, i.e. as root. The fix is to change the owner of the .npm folder back to yourself instead of root with command chown

    $ sudo chown -R my.user ~/.npm
  • If you install packages locally without first having them declared as dependencies in the package.json file, you are able to install them but will get an extraneous error, which indicates that the package is extraneous to the project.

    • To remove an extraneous package, use the npm command prune

      $ npm prune <name>
    • To install a package as well as having it declared as a dependency in your package.json file at the same time, use the --save parameter when installing, or the --save-dev parameter to have it declared as a devDependency

      $ npm install <package> --save
      $ npm install <package> --save-dev