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

@wingy3181/test-npm-publish

v0.0.4

Published

## Overview

Readme

Test-npm-publish

Overview

A repo to test publishing an npm package.

How this repository was created

The following steps were run:

  1. mkdir test-npm-publish
  2. cd test-npm-publish
  3. npm init --scope=@wingy3181 -y (and optionally change any values in package.json like the version number. license and npm scripts)
  4. echo "console.log('test-npm-publish');" > index.js && touch README.md (and these instructions were written inside README.md)
  5. git init && g cup
  6. Empty remote repository was created on GitHub via browser UI
  7. Following git commands were run to push local code to GitHub
    git remote add origin [email protected]:wingy3181/test-npm-publish.git
    git branch -M main
    git push -u origin main

How this repository was published to npm registry

The following steps were run:

  1. npm adduser and entered npm registry details to login
  2. npm publish --access=public

How to consume this package published to the npm registry

Run npm install @wingy3181/test-npm-publish within a npm project

How to unpublish package from registry

To unpublish a single version of a package, run npm unpublish @wingy3181/[email protected]

NOTE:

  • If you do not specify a version or if you remove all of a package's versions then the registry will remove the root package entry entirely.
  • Even if you unpublish a package version, that specific name and version combination can never be reused. In order to publish the package again, you must use a new version number.

To unpublish the entire package, run npm unpublish @wingy3181/test-npm-publish --force

NOTE:

  • If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.

References