Skip to content
forked from joebowbeer/regsync

Publish (migrate) node package versions from one registry to another

Notifications You must be signed in to change notification settings

uswitch/regsync

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

28 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

@uswitch/regsync - forked from @joebowbeer/regsync

Publish package versions from one registry into another.

Setup

npm install npm run build

Using the script

node ./dist/cli.js --name @scope/pkgname \
 --from.registry https://registry.npmjs.org/ --from.token $NPM_TOKEN \
 --to.registry https://npm.pkg.github.com --to.token $GITHUB_TOKEN

This will migrate all the versions that it can find on the "FROM.REGISTRY" that are missing on the "TO.REGISTRY"

If new versions of the package are published to the ORIGIN registry, they'll need to be migrated again in the future.

I'td be best to ensure that the package you're dealing with is automatically published to the new registry as part of its CI process.

About

Publish (migrate) node package versions from one registry to another

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 84.3%
  • JavaScript 15.7%