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 🙏

© 2025 – Pkg Stats / Ryan Hefner

package-transfer

v0.5.0

Published

Simple utility to transfer packages from your dependencies or devDependencies lists into new project.

Readme

package-transfer

npm Build Status Coverage Status

Simple utility to transfer packages from your dependencies or devDependencies lists into new project.

Install

npm install -g package-transfer

Usage

pkg-transfer [options]

Transfer dependencies from old-project to current project (my-new-project):

cd my-new-project
pkg-transfer -s ../old-project

The command detects which packages need to be transferred and offers to auto install them into target package.

This command does exactly the same thing only for devDependencies:

pkg-transfer -s ../old-project --dev

If you prefer yarn over npm:

pkg-transfer -s ../old-project --yarn

Strict mode

Most of the time you are locking your package.json dependencies to exact version. If you wish to transfer those exact versions to target package.json then just use --strict argument.

pkg-transfer -s ../my-project --strict

Help

Usage: pkg-transfer [options]

Options: -v, --version Print version --verbose Increase logging verbosity -h, --help Output help and usage information -s, --source Source package (from where you want to transfer dependencies) -t, --target Target package (defaults to current directory) --yarn Use yarn instead of npm --dev Transfer devDependencies --dry-run Just prints install command, does NOT really install anything --strict Use exact versions from source package.json when installing dependencies