npm

Node.js Package Registry

pckgs.io provides a npm registry for scoped Node.js packages. It speaks the npm protocol so the standard npm client installs and publishes against it with granular access control to strictly manage who can reach each package across your team.

Get Started View npm Docs

Quick Start

1. Authenticate

.npmrc

@my-scope:registry=https://npm.pckgs.io/my_org/
//npm.pckgs.io/my_org/:_authToken=ACCESS_TOKEN

2. Install

user@pckgs:~

npm install @my-scope/my-package

1. Configure package.json

package.json

{
  "name": "@my-scope/my-package",
  "version": "1.0.0",
  "publishConfig": {
    "registry": "https://npm.pckgs.io/my_org/"
  }
}

2. Configure .npmrc

.npmrc

@my-scope:registry=https://npm.pckgs.io/my_org/
//npm.pckgs.io/my_org/:_authToken=ACCESS_TOKEN

3. Publish

user@pckgs:~

npm publish

Why npm teams choose pckgs.io

Native npm CLI compatibility

No plugins, custom wrappers, or vendor CLIs required. The standard npm client connects directly via .npmrc out of the box.

Per-package access control

Define broad access with wildcards or target specific packages with read, write, or delete permissions for CI/CD pipelines and team members.

Public & Private package access

Publish private packages restricted to your organization or distribute public packages globally managed effortlessly within a single scoped registry.

Docs

Get Started

Get Started with npm

Authenticate

Configure `.npmrc` with your scope and access token.

Publish a package

Push your first npm package.

Install a package

Add npm packages to your project.

Import a package

Pull packages from another npm registry.

Other Registries

Unity Dart NuGet Go Cargo