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

sk-test-node-deploy

v1.0.13

Published

CLI tool to quickly scaffold a Node.js boilerplate project

Readme

NPM Package Workflow Guide

This repository contains commonly used commands for creating, testing, and publishing an npm package.


Initialize NPM Project

npm init

NPM Authentication

Login to NPM

npm login

Logout from NPM

npm logout

Local Package Linking (For Testing)

Use this to test your npm package locally before publishing.

Link Package Locally

npm link

Unlink Package Locally

npm unlink -g <package-name>

Publishing NPM Package

Publish Without 2FA

npm publish --access public

Standard Publish

npm publish

Update NPM Package

Increase patch version and publish:

npm version patch
npm publish --access public

Other version options:

  • npm version minor
  • npm version major

Package Information

Check if Package Already Exists

npm view <package-name>

Check Package Owner

npm owner ls <package-name>

Bypass 2FA Using NPM Token

Configure npm authentication token (useful for CI/CD):

npm config set //registry.npmjs.org/:_authToken=<YOUR_NPM_TOKEN>

⚠️ Important: Never commit your npm token to source control.


Notes

  • Always update the version before publishing
  • Test locally using npm link
  • Ensure package name is unique
  • Enable 2FA for better security