🔑 npm-token.prusa3d.dev
Internal

NPM Token Setup

Configure access to @prusa3d-platform private packages.
One command to set up your local development environment.

Quick Setup

The scripts are behind Cloudflare Access, so they are fetched through cloudflared. Install it and log in once, then run setup:

# once: install cloudflared and log in (re-run login when it expires)
brew install cloudflared
cloudflared access login https://npm-token.prusa3d.dev
# once: install cloudflared and log in (re-run login when it expires)
winget install --id Cloudflare.cloudflared
cloudflared access login https://npm-token.prusa3d.dev
cloudflared access curl https://npm-token.prusa3d.dev/setup | bash
cloudflared access curl https://npm-token.prusa3d.dev/setup.ps1 | Out-String | iex

Creates a new token, or validates existing one. If token is expired or invalid, prompts to create a new one.

Revoke Token

To revoke your token and remove local configuration:

cloudflared access curl https://npm-token.prusa3d.dev/revoke | bash
cloudflared access curl https://npm-token.prusa3d.dev/revoke.ps1 | Out-String | iex

Revokes the token via GitLab API and removes the local token file.

What it does

🔑
Creates GitLab PAT
Opens GitLab with pre-filled token settings (api scope, 30 days expiry)
💾
Stores securely
Linux/macOS: ~/.config/prusa/npm-token (chmod 600)
Windows: %LOCALAPPDATA%\Prusa\npm-token (restricted ACL)
⚙️
Configures shell
Linux/macOS: Adds export to .zshrc / .bashrc
Windows: Sets persistent User environment variable
✅
Validates token
Checks if existing token is valid, expired, or needs renewal

Manual Setup

If you prefer to set things up manually:

  1. Create a GitLab Personal Access Token with api scope
  2. Add the token to your environment:

    Add to ~/.zshrc or ~/.bashrc:

    export NPM_PRUSA_PLATFORM_TOKEN="glpat-your-token-here"

    Run in PowerShell:

    [Environment]::SetEnvironmentVariable("NPM_PRUSA_PLATFORM_TOKEN", "glpat-your-token-here", "User")

    Or: Settings → System → About → Advanced system settings → Environment Variables

  3. Create .npmrc in your project: 
    @prusa3d-platform:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken="${NPM_PRUSA_PLATFORM_TOKEN}"
    @prusa3d-platform:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=${NPM_PRUSA_PLATFORM_TOKEN}

    Note: On Windows, use ${VAR} without quotes.

Troubleshooting

npm install fails with E401

Your token is invalid or expired. Run the setup command again:

cloudflared access curl https://npm-token.prusa3d.dev/setup | bash
cloudflared access curl https://npm-token.prusa3d.dev/setup.ps1 | Out-String | iex
Token not found after setup

The token is loaded when you start a new shell. Either:

  • Open a new terminal
  • Or run: source ~/.zshrc

Environment variables require a new terminal session. Either:

  • Open a new PowerShell / Terminal window
  • Or refresh variables in current session
Permission denied on token file

Fix permissions:

chmod 600 ~/.config/prusa/npm-token
chmod 700 ~/.config/prusa

Reset file permissions (PowerShell as Administrator):

$path = "$env:LOCALAPPDATA\Prusa\npm-token"
icacls $path /reset
icacls $path /inheritance:r /grant:r "$($env:USERNAME):(R,W)"
PowerShell execution policy error (Windows)

If you see "running scripts is disabled on this system", run PowerShell as Administrator:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Then try the setup command again.

Download and run scripts manually (Windows)

If you're having issues with the remote execution, you can download the scripts and run them locally:

  1. Download the scripts:
    • setup.ps1 from https://npm-token.prusa3d.dev/setup.ps1
    • revoke.ps1 from https://npm-token.prusa3d.dev/revoke.ps1
  2. Unblock the downloaded file(s): 
    Unblock-File .\setup.ps1
Unblock-File .\revoke.ps1
  3. Execute the script: 
    .\setup.ps1

    Or for revoke:

    .\revoke.ps1