Artifactory Repository Manager

Teams using JFrog Artifactory can manage access to NES packages through 3 easy steps:

Create a Remote Repository (NES Remote Repository) for our private NPM registry.
Configure (or create) a Virtual Repository to leverage the newly created NES Remote Repository

Important

This Virtual Repository is mandatory as a misconfiguration will lead to Artifactory seeking all NPM packages from us. Failure to configure this correctly may result in suspension of your access token.

Verify your developers are able to access our package through your Virtual Repository.

Step 1: Create a Remote Repository

Navigate to Artifactory > Repositories > Remote
Select Create > Remote Repository, then select NPM as the type
Configure the following on the Basic tab:

"Step 1"

Repository Key: nes (or whatever alias your team prefers)
URL: https://registry.nes.herodevs.com/npm/pkg
Username: artifactory
Password: <your NES access token>
Include Patterns:
1. Click the x to delete the default **/* pattern
2. Add .npm/@neverendingsupport/**
3. Add @neverendingsupport/**
Remote Mapping Layout: npm-default

Configure the following on the Advanced tab:

"Step 1"

Ensure Bypass HEAD Requests is checked
Ensure Disable URL Normalization is checked

The final results should look similar to the following:

Basic

"Result-Basic"

Note

Our registry does not implement every endpoint in the public NPM registry. As such, some Artifactory features may not function as expected, such as the "Test" button or various search features.

Advanced

"Result-Advanced"

Step 2: Configure a Virtual Repository

In this step, you should configure the virtual repository referenced in the .npmrc files. This step is fairly straight forward, and only requires adding our private NPM registry after the public npmjs.org registry.

Assumptions:

You already configured a Remote Repository for npmjs.org keyed as npm-official
You already configured a Remote Repository for our registry keyed as nes (see Step 1)

If you already have a Virtual Repository configured with npm-official (and potentially other private sources) you can skip the following steps.

Navigate to Artifactory > Repositories > Virtual
Select Create > Virtual Repository, then select NPM as the type

Whether creating or editing a new Virtual Repository, add both npm-official and nes repositories to Selected Repositories with nes at the bottom of the list.

In most versions of Artifactory, you should see the following:

"Virtual-Setup"

Step 3: Verify Access

Assuming again your Virtual Repository is keyed as npm-default and that you have a valid Artifactory username / password, configure your .npmrc accordingly:

@neverendingsupport:registry=<artifactory_url>/artifactory/api/npm/<virtual_repository_key>/
<artifactory_url>/artifactory/api/npm/<virtual_repository_key>/:_password=<base64_artifactory_password>
<artifactory_url>/artifactory/api/npm/<virtual_repository_key>/:username=<artifactory_email>
<artifactory_url>/artifactory/api/npm/<virtual_repository_key>/:email=<artifactory_email>
<artifactory_url>/artifactory/api/npm/<virtual_repository_key>/:always-auth=true

Once configured, Artifactory will attempt to download packages under the @neverendingsupport namespace from our private registry.