Create and Manage a Project's Remote NPM Registry Connection

If your project users access the remote default NPM registry frequently, you can create a pre-defined connection for them. Project users can then configure a job and use the connection to access as well as publish scoped and unscoped packages in the default NPM registry while running builds.

To create a connection, you’ll need the credentials of a user who can access the remote NPM registry.

You must be a project owner to add and manage the remote NPM registry:

Action	How To
Add a remote NPM registry connection	In the left navigator, click Project Administration . Click Builds. Click the NPM Connection tab. Click Add NPM Connection. In the Create NPM Connection dialog box, in Connection Name, enter a unique name. In Username and Password, enter the credentials of a user who has access to the remote NPM registry. In Registry URL, enter the Registry URL for the default remote NPM registry, for example https://registry.npmjs.org. Click Create.
Edit a connection and change the connection’s user credentials or provide another Registry URL	In the left navigator, click Project Administration . Click Builds. Click the NPM Connection tab. Click Edit for the NPM connection you want to edit. In the Edit NPM Connection dialog box, if necessary, enter the credentials of a user who has access to the remote NPM registry. In Registry URL, if necessary, enter the URL for the default remote NPM registry. Click Update.
Delete the connection	In the left navigator, click Project Administration . Click Builds. Click the NPM Connection tab. Click to delete the NPM connection. In the Delete NPM Connection dialog box, click Delete.