Registry and authentication

aube uses npm registry protocols and pnpm-compatible .npmrc configuration.

Registries

registry=https://registry.npmjs.org/
@acme:registry=https://registry.example.test/

The global --registry flag overrides the default registry for one command:

aube --registry=https://registry.example.test install

Commands such as publish, login, logout, deprecate, undeprecate, and unpublish also accept their own --registry flag.

Tokens

Keep the token value in the environment and commit only its placeholder in a project .npmrc. Match the token's host and path to the registry URL:

//registry.npmjs.org/:_authToken=${NPM_TOKEN}

Log in interactively or with a pasted token:

aube login
aube login --scope @acme --registry https://registry.example.test/
aube logout --scope @acme

aube login stores credentials in npm-compatible user configuration. Use a scoped registry when only your organization's packages should use that host.

To inspect the selected default registry without printing a full config dump:

aube config get registry

Proxies and TLS

aube reads common npm proxy and TLS settings:

https-proxy=http://proxy.example.test:8080
noproxy=localhost,127.0.0.1
strict-ssl=true
cafile=/path/to/corp-ca.pem

Cache tools

aube cache list
aube cache view react
aube cache delete '@babel/*'
aube cache list-registries

These commands inspect cached registry metadata (also called packuments). Package files live separately in the content store printed by aube store path.