Registry access

The @systhemaui/* packages live on a private GitHub Packages registry. Every Systhema project, including the ones systhema create scaffolds, has to authenticate against it before pnpm install can fetch them.

Getting accessLink to this section

Access comes with a Systhema licence. It is granted as a GitHub personal access token (classic) with the read:packages scope.

Configure the projectLink to this section

Two files do the work. .npmrc points the @systhemaui scope at the registry and reads the token from the environment:

@systhemaui:registry=https://npm.pkg.github.com/systhemaui
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

You can store the token in a trusted local .env file. pnpm does not load that file automatically. Keep it out of version control and export the token before installation:

GITHUB_TOKEN=ghp_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Scaffolded projects already ship the .npmrc; you only add the token.

Export the tokenLink to this section

Export the token before installing dependencies:

# Load a trusted, shell-compatible .env file.
set -a
. ./.env
set +a

# Or add it to your shell profile so it's always available:
# ~/.zshrc / ~/.bashrc
export GITHUB_TOKEN=ghp_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

TroubleshootingLink to this section

• If pnpm install fails with a 401 or 404 against npm.pkg.github.com, check that the token has the read:packages scope and that it is exported in the shell where you run pnpm.
• Keep the token active. Package installs fail immediately once it expires.