loading...

re: GitHub announces GitHub Package Registry VIEW POST

FULL DISCUSSION
 

Assuming I understand package registries, I'm not sure what problem GitHub is trying to solve with their own package registry. Is the point of this so that your source code will be on GitHub and the package will also be published there, so it is a "one-stop shop"? Will I still need to use npm's/yarn's CLI for JavaScript, but change where it downloads the packages from? If I understand that correctly, it would seem like a hassle if only some packages I am using are on GitHub's registry, but all of them are on npm's registry. Wouldn't it make sense just to use npm?

Is this more beneficial to enterprise customers that already use GitHub for their code so that they can have their private packages published in GitHub's registry instead of npm Enterprise or setting up and maintaining their own registry?

code of conduct - report abuse