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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@appsweet-co/npm-carbon

v2.0.0

Published

Copy npm packages and all their versions from one registry to another

Downloads

8

Readme

Based on goodeggs/npm-copy and dperuo/npm-carbon.

Use this command line tool to make a "carbon copy" of any npm package and all its published versions.

ESM vs CJS

We migrated to ESM starting in v2.0.0. Please use v1 if you need CommonJS modules.

Install

No installation needed. Use @appsweet-co/npm-carbon directly from the command line.

Node

npx @appsweet-co/npm-carbon -s $SRC_URL -d $DEST_URL <OPTIONS>

Bun

bunx @appsweet-co/npm-carbon -s $SRC_URL -d $DEST_URL <OPTIONS>

Usage

Run --help for a full list of options.

npx @appsweet-co/npm-carbon --help

Authenticate Using Auth Tokens

npx @appsweet-co/npm-carbon \
  --src https://registry.npmjs.org \
  --dest https://registry.npmjs.org \
  --srcToken w7ikVizKsyP98uyBS6 \
  --destToken JmNMqitWbnOex3py9A \
  packageA [packageB...]

Authenticate Using Username, Password, and Email

npx @appsweet-co/npm-carbon \
  --src https://registry.npmjs.org \
  --srcUser helloworld \
  --srcPassword https://registry.npmjs.org \
  --srcEmail [email protected] \
  --dest https://registry.npmjs.org \
  --destUser helloworld \
  --destPassword gUbcneqpbxC8 \
  --destEmail [email protected] \
  packageA [packageB...]

Specify a Version Range

By default, @appsweet-co/npm-carbon copies all avaliable versions of the package. Use --range to specify a subset of versions.

The --range flag accepts any valid npm version range/

npx @appsweet-co/npm-carbon \
  --range "~3.0.0 || 5.1.x" \
  packageA [packageB...]

Modify Package Prefix

Modify the package prefix using the --srcprefix and --destPrefix flags.

npx @appsweet-co/npm-carbon \
  --srcPrefix @company \
  --destPrefix @company \
  packageA [packageB...]

:warning: WARNING: List packages without their prefix when using the prefix flags. Example: @foo/packageA becomes just packageA.

-----------------------------------------------------

Contributing

Contributions, issues and feature requests are welcome! Feel free to check issues page.

Install

Clone this repo to your local machine and install dependencies.

git clone https://github.com/appsweet-co/npm-carbon.git
cd npm-carbon/
npm install

Usage

Use the start command to compile TypeScript and watch for changes.

npm start

Run the local JavaScript file directly to check your changes.

node ./bin/index.js <OPTIONS>

Run Tests

Run the full test suite using the test command.

npm run test

Submit Your Pull Request

Always submit your Pull Request against main.