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

pkgmigr8or

v1.1.0

Published

A CLI tool to help you migrate packages from NPM to a private registry

Readme

pkgmigr8or

pkgmigr8or (Package migrater) is a Migration CLI tool to export packages from NPM to a private registry e.g. Verdaccio.

Installation

npm install -g pkgmigr8or

Pre-Requisites

Authentication

To migrate any of your packages from NPM you will need to have your account logged in using npm adduser.

If your private registry also has auth permissions required to publish you will need to have logged in to that as well, also using npm adduser passing in the --registry-url flag.

You can cat ~/.npmrc and should be able to see tokens for both registries.

Usage

Create a directory somewhere and point your CLI in to it.

The script takes 2 arguments:

  1. A file which contains a list of all the packages you want to export.
  2. The URL of your private registry you are migrating to.
pkgmigr8or packages.txt http://localhost:4873

Defining your packages.

Create a plain text file in your directory e.g. packages.txt.

Each line represents a new package

myPackage
@myScope/myPackage

Restricting vesrions.

You may not want to get every version ever published of your package for migration. The script will recognise a # in your package name as a version delimiter and for each package of that name will only download packages that satisfy the version constraints based on semver.satisfies. If you don't specify a #, all versions ever published will be migrated.

myPackage#<=1.0.2
@myScope/myPackage#>1.0.2 <2.0.0