Private registry access

@kanunilabs/pivotgrid-react-enterprise is not published on public npm. It installs from our private registry at registry.kanunilabs.com, and every license comes with its own registry credentials: a username like cust_ab12cd34 and a password.

Where your credentials come from

You can get them in two places:

1. Purchase email — the "Your license is ready" email contains a ready-to-paste .npmrc block under Private npm registry.
2. Dashboard — Dashboard → Licenses, open your license, and use the Private npm registry section.

For security we store only a hash of your password — it can never be displayed again after it is first shown. Losing it is not a problem: regenerating takes one click (see below).

Set up your project

Put the three lines from your email (or the dashboard) into a .npmrc file next to your package.json:

@kanunilabs:registry=https://registry.kanunilabs.com/
//registry.kanunilabs.com/:_auth=<value from your email or dashboard>
//registry.kanunilabs.com/:always-auth=true

Then install as usual:

npm install @kanunilabs/pivotgrid-react-enterprise

The first line routes only the @kanunilabs scope to our registry — which also transparently serves the public @kanunilabs/pivotgrid-core and -react packages, so everything else about your setup stays unchanged.

Keeping the token out of git (teams & CI)

.npmrc contains a secret, so either add it to .gitignore, or commit a variable version and inject the value from the environment — npm expands ${VAR} inside .npmrc:

@kanunilabs:registry=https://registry.kanunilabs.com/
//registry.kanunilabs.com/:_auth=${KANUNILABS_REGISTRY_AUTH}
//registry.kanunilabs.com/:always-auth=true

Set KANUNILABS_REGISTRY_AUTH (the _auth value from your email or dashboard) as a CI secret or in your local shell.

Lost or leaked password? Regenerate it

1. Sign in at kanunilabs.com/dashboard.
2. Open Licenses and click your license.
3. In the Private npm registry section, click Regenerate credentials (or Generate credentials if you never had any).
4. Copy the new .npmrc block right away — it is shown only once.

⚠️ Regenerating invalidates the previous password immediately. Update every place that uses it (developer machines, CI secrets) at the same time, or their npm install will start failing with 401.

Your registry username never changes when you regenerate — only the password does.

Troubleshooting

Still stuck? Open a support ticket — we're happy to help.