Better Programming

Advice for programmers.

Follow publication

Member-only story

Everything You Need To Know About The GitHub Package Registry

Trevor-Indrek Lasn
Better Programming
Published in
3 min readSep 25, 2019
GitHub is accepting early users for the package registry

GitHub opened the door for a bunch of users to test their package registry. But what exactly is the GitHub Package Registry, and how does it differentiate from other package registers, such as npm?

The GitHub Package Registry is a software-package hosting service, similar to npmjs.org, rubygems.org, or hub.docker.com, that allows you to host your packages and code in one place. You can host software packages privately or publicly and use them as dependencies in your projects.

Github Packages tab

The GitHub Package Registry allows you to develop your code and host your packages in one place. You can use packages from the GitHub Package Registry as a dependency in your source code on GitHub.

GitHub uses the README in your repository to generate the package’s description, and you can edit it to reflect details about the package or installation process. GitHub adds metadata for each package version that includes links to the author, repository, commit SHA, version tags, and date. To see an example registry package page, see the @Codertocat/hello-world-npm package.

hello-world-npm package

To install the package, follow the instructions below.

If you’re part of the beta program, you can see packages appear on your GitHub profile. and you can also publish packages on GitHub.

New Packages tab on Github

Publishing a Package

You can set up the scope mapping for your project using either a local .npmrc file in the project or using the publishConfig option in…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Responses (2)

Write a response