Skip to contentSkip to Content
Private registry

Private registry

Use your team’s private components and packages in prototypes with your Artor account. An admin connects the package source once; teammates don’t need its shared access token.

How designers use it

Private packages are available on Enterprise. If your organization has connected them, Artor sets up access when you create or pull a prototype. For an existing project, run:

artor registry login

You can then install your team’s packages, such as @acme/button, in that project. If the organization’s registry proxy isn’t available (it’s turned off, or the plan doesn’t include it), artor registry login says so and leaves .npmrc unchanged. Your coding agent can help add them. See Installing the CLI if you haven’t set up the terminal yet.

This setup stores your Artor login token in the project’s .npmrc file. Treat it like a password: add .npmrc to .gitignore and don’t share the file. Artor excludes it when publishing or downloading prototype source.

How to set it up (admin)

An owner or admin connects the private package source using its access token. For example:

artor registry add @acme --type azure \
  --uplink https://pkgs.dev.azure.com/acme/_packaging/feed/npm/registry \
  --token <your-azure-token> --expires 2026-12-31  # admin access required
 
artor registry add @beta --type npmjs --token <your-npm-token>  # admin access required

Use a token that permits package downloads. Instead of --token, you can supply it through ARTOR_REGISTRY_TOKEN. Artor does not show the saved token again or distribute it to teammates.

artor registry list          # see connected sources
artor registry list --json   # the same, for scripts
artor registry rm @acme      # remove a source; admin access required

registry list shows every connected source, with a note when the proxy isn’t available. With --json it prints a bare array ([] when nothing is connected) and each row adds proxyAvailable: true, false (registry login writes nothing), or null from an older Artor server. The note goes to the error output so the JSON stays clean. See Scripting & agents.

To renew a token, run registry add again for the same package scope, including the new token and any changed source address or expiry.

Access and limits

  • Adding or removing sources requires an owner or admin.
  • Organization members can list sources and set up package installation.
  • This connection installs packages; it cannot publish packages to the source.
  • Adding a source requires Enterprise. After a downgrade, you can still list and remove previously connected sources.
Mock datasetsJoining an organization