Accessing a github npm registry with gh

Jun 06, 2024

If you've published a package to github's npm registry, the documentation tells you to create a Personal Access Token. This is an unfortunately un-scriptable process.

Thankfully, it is possible to use the gh command line tool to create a usable token. Since it's poorly documented, I've written this note; it assumes you have gh installed already.

  1. gh auth login --scopes=write:packages
    1. This will guide you through a process to create a token with write:packages scope, which allows you to read and write npm packages to the github repository
  2. npm config set -g // $(gh auth token)
    1. This globally configures npm to use the token you just generated when authenticating to
  3. npm config set -g @your_scope:registry
    1. This command globally configures npm to use the github package registry for the scope containing your package
    2. My advice is to use a particular scope for the packages you want to live on the github package repository; it is not easily possible to have npm switch between registries if you have some packages on regular npm and others on the github package repository

To test that you have access, you can do npm install -g @your_scope/some_package and verify that you are able to install your private package.

There's an open issue in the gh cli repository for how to integrate this process better, but I'm not exactly sure how it would work. There's also an issue for using gh with docker, so you can avoid creating a token there too.

↑ up