npm Registry

Drok's npm registry is a full-featured npm-compatible package registry. Publish scoped and unscoped packages, install dependencies, and manage access — all through the standard npm CLI.

Configuration

Configure npm to use Drok as your registry for your organization's scope:

npm config set @your-org:registry https://drok.us/api/v1/packages/npm/your-org/
npm config set //drok.us/api/v1/packages/npm/your-org/:_authToken YOUR_Drok_TOKEN

Or add to your project's .npmrc:

@your-org:registry=https://drok.us/api/v1/packages/npm/your-org/
//drok.us/api/v1/packages/npm/your-org/:_authToken=${Drok_TOKEN}

Publishing

Publish packages using the standard npm workflow:

npm publish

Ensure your package.json uses your organization's scope:

{
  "name": "@your-org/my-package",
  "version": "1.0.0"
}

Publishing from Pipelines

# .lehub/pipeline.yml
stages:
  - name: publish
    when: tag =~ "v*"
    steps:
      - name: Publish to npm registry
        run: npm publish
        secrets: [Drok_TOKEN]
        env:
          NPM_CONFIG_REGISTRY: https://drok.us/api/v1/packages/npm/$ORG/

Installing

Install packages from Drok alongside public npm packages:

npm install @your-org/my-package

npm resolves @your-org scoped packages from Drok's registry and all other packages from the public npm registry, as configured in .npmrc.

Features

• Scoped and unscoped packages — Both @scope/package and plain package names are supported
• Tarball hosting — Package tarballs are stored on Drok's infrastructure
• Metadata API — Full npm registry metadata API compatibility
• Provenance — Packages published from Drok Pipelines include build provenance attestations
• Dist-tags — Manage distribution tags (latest, next, beta) via npm dist-tag

CLI Commands

# Publish
npm publish
 
# Install
npm install @your-org/my-package
 
# View package info
npm view @your-org/my-package
 
# List versions
npm view @your-org/my-package versions
 
# Deprecate a version
npm deprecate @your-org/my-package@1.0.0 "Use 2.0.0 instead"