How to use the GitHub Package Registry

By now I’m sure most of you are aware that GitHub has launched its own package registry, which is now in beta. If you haven’t already had any exposure to it, today I’m going to take you through deploying a NodeJS package to the GitHub Package Registry. This is super exciting for a few reasons. One reason is that this is not just limited to NodeJS packages. If you go to the official website, you will see that you can deploy Docker images, Maven packages for Java, NuGet packages for C#, and Ruby Gems.

Another, more obvious, reason is the tight integration with GitHub. With any luck, this will make deploying and maintaining packages a whole lot easier because there will only be a single place for you to deploy to (we’re going to test that theory). The last reason is that you can also publish private packages. If you were to use NPM, for example, you would have to pay $7/team member/month for private packages. That’s not the biggest cost in the world, but GitHub now allows you free private repositories which means your private packages can now be free as well.

Getting Started

Let’s get started with our package! As I mentioned, we’re going to deploy an…