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

@caselaw-elibrary/common

v1.0.15

Published

Logout from any existing npm sessions to avoid conflicts:

Readme

How to Login

Prerequisites

Logout from any existing npm sessions to avoid conflicts:

npm logout

Step 1: Generate a New npm Access Token

You must generate a new access token on the npm website with specific permissions.

  1. Log in to your account on the npm website.
  2. Navigate to Account Settings (your profile icon in the top right).
  3. Select Access Tokens from the menu.
  4. Click the "Generate New Token" button.
  5. Configure the Token:
    • Token Type: Select "Publish". This grants the token the ability to publish new packages and versions.
    • Crucial Step: Ensure you check the box for "Bypass 2FA for publishing" (or a similarly worded option). This is the key requirement to resolve the E403 error without an OTP.
  6. Click "Generate Token" and immediately copy the token that is displayed. You will not be able to view it again.

Step 2: Configure the Token in Your Environment

You need to tell the npm CLI to use this new token when communicating with the registry.

Option A: Local .npmrc File (Development)

Run the following command in your terminal, replacing <YOUR_NEW_TOKEN> with the token you copied in Step 1.

npm set //registry.npmjs.org/:_authToken <YOUR_NEW_TOKEN>