npm install fails with E404 — package not found on npmjs.org

[rucka]

Description
Installing @foomakers/pair-cli via npm install -g fails with a 404 error because the package is hosted on GitHub Packages, not on the public npm registry (registry.npmjs.org).
The README Quick Start section suggests running:
npx @foomakers/pair-cli install
This also fails out of the box for the same reason — npm defaults to registry.npmjs.org, where the package does not exist.
Steps to Reproduce

Run npm install -g @foomakers/pair-cli (or npx @foomakers/pair-cli install) with a default npm configuration
Observe E404 error:
npm error 404 Not Found - GET https://registry.npmjs.org/@foomakers%2fpair-cli - Not found

Expected Behavior
The package should install without requiring manual .npmrc configuration, or the README should document the required setup (GitHub PAT + .npmrc registry override for the @foomakers scope).
Suggested Fix
Either:

Publish the package to the public npm registry so npx works out of the box, or
Add installation prerequisites to the README explaining how to configure .npmrc for GitHub Packages

Environment

npm 10.x
macOS
No custom .npmrc configuration

[rucka]

Workaround — How to install while we fix the docs

The package is currently hosted on GitHub Packages, so you need two things before installing:

1. Generate a GitHub Personal Access Token

Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic) and create a token with the read:packages scope. Any GitHub account works — you don't need to be a member of the org.

2. Configure .npmrc

Add the following to ~/.npmrc (or to a project-level .npmrc):

@foomakers:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN

3. Install

npx @foomakers/pair-cli install

This applies to npm, pnpm, and yarn — they all read .npmrc.

---

We acknowledge this is a friction point, especially for an open-source project whose README implies a zero-config npx experience. We'll update the documentation with these prerequisites as a first step, and evaluate publishing to the public npm registry as a longer-term fix.