Moving my public NPM package from Bitbucket to Github -


i bitbucket better github, sadly there's few options continuous integration bitbucket.

the packages in question written me, , hosted on bitbucket:

i want these moved github, without breaking anything. afraid changing repository data not enough.

  "repository": {     "type": "git",     "url": "https://stephanbijzitter@bitbucket.org/skelware/grunt-asset-compress.git"   }, 

image user has version 1 installed, hosted on bitbucket. change version 2 , change url github url. proceed push, both github , bitbucket. if user updates, updating version 2, includes url of github. push more fixes , release version 3 on github, user updates again , fine.

however, if user did not update version 2, before version 3 released? npm try download version 3 bitbucket url points in version 1!

i not want keep repositories in sync; want able make bitbucket repository private @ 1 point hide public view while github repository serve on own.

what steps need take able move github, without breaking update system (albeit limited) users of packages?

just got reply npm itself:

hi, stephan.

thanks question. i'm hoping can help...if i'm understanding inquiry correctly.

what ever publish npm held within our own repository , what's served user when install package. inclusion of repository url, bitbucket or github, more informational opposed functional. regardless of when push changes github, user installs package latest publish npm. in other words, 2 things may in different states , @ different versions.

please let me know if i'm off base. i'll here help. ernie

in other words, care remove bitbucket repository entire , nothing break, copy hosted on servers served downloading through npm.

thank you, ernie!


Comments

Popular posts from this blog

php - Invalid Cofiguration - yii\base\InvalidConfigException - Yii2 -

How to show in django cms breadcrumbs full path? -

ruby on rails - npm error: tunneling socket could not be established, cause=connect ETIMEDOUT -