Artifactory allows you to define any layout for your npm regsitries. In order to upload packages according to your custom layout, you need to package your npm files using
This creates the .tgz file for your package which you can then upload to any path within your local npm repository.
Remote Npm Registry
A Remote Repository defined in Artifactory serves as a caching proxy for a registry managed at a remote URL such as
Artifacts (such as tgz files) requested from a remote repository are cached on demand. You can remove downloaded artifacts from the remote repository cache, however, you can not manually deploy artifacts to a remote npm registry.
To define a remote repository to proxy a remote npm registry follow the steps below:
- In the Admin module, under Repositories | Remote, click "New".
- In the New Repository dialog, set the Package Type to npm, set the Repository Key value, and specify the URL to the remote registry in the URL field as displayed below
- Click "Save & FInish"
Virtual Npm Registry
A Virtual Repository defined in Artifactory aggregates packages from both local and remote repositories.
This allows you to access both locally hosted npm packages and remote proxied npm registries from a single URL defined for the virtual repository.
To define a virtual npm registry, create a virtual repository, set the Package Type to be npm, and select the underlying local and remote npm registries to include in the Basic settings tab.
Click "Save & Finish" to create the repository.
The fields under External Dependency Rewrite are connected to automatically rewriting external dependencies for npm packages that need them.
Enable Dependency Rewrite
|When checked, automatically rewriting external dependencies is enabled.|
Remote Repository For Cache
|The remote repository aggregated by this virtual repository in which the external dependency will be cached.|
A white list of Ant-style path expressions that specify where external dependencies may be downloaded from. By default, this is set to
For example, if you wish to limit external dependencies to only be downloaded from
Using the Npm Command Line
When accessing an npm repository through Artifactory, the repository URL must be prefixed with api/npm in the path. This applies to all npm commands including
For example, if you are using Artifactory standalone or as a local service, you would access your npm repositories using the following URL:
Or, if you are using Artifactory SaaS the URL would be:
To use the npm command line you need to make sure npm is installed. Npm is included as an integral part of recent versions of
Please refer to
Once you have created your npm repository, you can select it in the Tree Browser and click Set Me Up to get code snippets you can use to change your npm registry URL, deploy and resolve packages using the npm command line tool.
Setting the Default Registry
For your npm command line client to work with Artifactory, you first need to set the default npm registry with an Artifactory npm repository using the following command (the example below uses a repository called
npm config set registry http://<ARTIFACTORY_SERVER_DOMAIN>:8081/artifactory/api/npm/npm-repo
For scoped packages, use the following command:
npm config set @<SCOPE>:registry http://<ARTIFACTORY_SERVER_DOMAIN>:8081/artifactory/api/npm/npm-repo
We recommend referencing a Virtual Repository URL as a registry. This gives you the flexibility to reconfigure and aggregate other external sources and local repositories of npm packages you deployed.
Note that If you do this, you need to use the
Authenticating the npm Client
Once you have set the default registry, you need to authenticate the npm client to Artifactory in one of two ways: using the
npm login command or using basic authentication.
Using npm login
npm login was introduced in version 5.4.
Run the following command in your npm client. When prompted, provide your Artifactory login credentials:
Upon running this command, Artifactory creates a non-expirable access token which the client uses for authentication against Artifactory for subsequent
npm install and
npm publish actions.
If the token is removed from Artifactory, the client will have to login again to receive a new token.
Using Basic Authentication
To support basic authentication you need to edit your
.npmrc file and enter the following:
- Your Artifactory username and password (formatted
Newtablink Text Base64 URL http://www.base64encode.org/
- Your email address (
npm publishwill not work if your email is not specified in
- You need to set
always-auth = true
You can use the following command to get these strings directly from Artifactory:
Where <CREDENTIAL> is your Artifactory password or API Key
Here is an example of the response:
If, in addition, you are also working with scoped packages, you also need to run the following command:
curl -uadmin:<CREDENTIAL> http://<ARTIFACTORY_SERVER_DOMAIN>:8081/artifactory/api/npm/auth/<SCOPE>
Where <CREDENTIAL> is your Artifactory password or API Key
Paste the response to this command in the ~/.npmrc file on your machine (in Windows, %USERPROFILE%/.npmrc).
Resolving npm Packages
Once the npm command line tool is configured, every
npm install command will fetch packages from the npm repository specified above. For example:
$ npm install request npm http GET http://localhost:8081/artifactory/api/npm/npm-repo/request npm http 200 http://localhost:8081/artifactory/api/npm/npm-repo/request npm http GET http://localhost:8081/artifactory/api/npm/npm-repo/request/-/request-2.33.0.tgz npm http 200 http://localhost:8081/artifactory/api/npm/npm-repo/request/-/request-2.33.0.tgz
Npm Publish (Deploying Packages)
Setting Your Credentials
The npm command line tool requires that sensitive operations, such as
publish, are authenticated as described under Authenticating the npm Client above.
Deploying Your Packages
There are two ways to deploy packages to a local repository:
- Edit your
package.jsonfile and add a publishConfig section to a local repository:
- Provide a local repository to the
npm publish --registry
Specifying the Latest Version
By default, the "latest" version of a package in an NPM registry in Artifactory is the one with the highest
artifactory.npm.tag.tagLatestByPublish = true
Working with Artifactory without Anonymous Access
By default, Artifactory allows anonymous access to npm repositories. This is defined in the Admin module under Security | General. For details please refer to Allow Anonymous Access.
If you want to be able to trace how users interact with your repositories you need to uncheck the Allow Anonymous Access setting. This means that users will be required to enter their username and password as described in Setting Your Credentials above.
Using OAuth Credentials
Artifactory uses GitHub Enterprise as its default OAuth provider. If you have an account, you may use your GitHub Enterprise login details to be authenticated when using
Artifactory supports a variety of ways to search of artifacts. For details please refer to Searching Artifacts.
Artifactory also supports
npm search [search terms ...], however, packages may not be available immediately after being published for the following reasons:
When publishing a package to a local repository, Artifactory calculates the search index asynchronously and will wait for a "quiet period" to lapse before indexing the newly published package.
Since a virtual repository may contain local repositories, a newly published package may not be available immediately for the same reason.
You can specify the indexing "quiet period" (time since the package was published) by setting the following system properties (in
In the case of remote repositories, a new package will only be found once Artifactory checks for it according to the Retrieval Cache Period setting.
Artifactory annotates each deployed or cached npm package with two properties:
You can use Property Search to search for npm packages according to their name or version.
Cleaning Up the Local Npm Cache
The npm client saves caches of packages that were downloaded, as well as the JSON metadata responses (named
The JSON metadata cache files contain URLs which the npm client uses to communicate with the server, as well as other ETag elements sent by previous requests.
We recommend removing the npm caches (both packages and metadata responses) before using Artifactory for the first time. This is to ensure that your caches only contain elements that are due to requests from Artifactory and not directly from
The default cache directory on Windows is
%APPDATA%\npm-cache while on Linux it is
Npm Scope Packages
Artifactory fully supports
By default, the npm client encodes slash characters ('/') to their ASCII representation ("%2f") before communicating with the npm registry. If you are running Tomcat as your HTTP container (the default for Artifactory), this generates an "HTTP 400" error since Tomcat does not allow encoded slashes by default. In order work with npm scoped packages, you can override this default behavior by defining the following property in the
Note that since Artifactory version 4.4.3, the bundled Tomcat is configured by default to enable encoded slashes. If you are using a previous version you will need to adjust the Tomcat property above.
If Artifactory is running behind a reverse proxy, make sure to disable URL decoding on the proxy itself in order to work with npm scope packages.
For Apache, add the "AllowEncodedSlashes NoDecode" directive inside the <VirtualHost *:xxx> block.
Configuring the npm Client for a Scope Registry
Using Login Credentials
Scopes can be associated with a separate registry. This allows you to seamlessly use a mix of packages from the public npm registry and one or more private registries.
For example, you can associate the scope
@jfrog with the registry
http://localhost:8081/artifactory/api/npm/npm-local/ by manually altering your
~/.npmrc file and adding the following configuration:
@jfrog:registry=http://localhost:8081/artifactory/api/npm/npm-local/ //localhost:8081/artifactory/api/npm/npm-local/:_password=cGFzc3dvcmQ= //localhost:8081/artifactory/api/npm/npm-local/:username=admin //localhost:8081/artifactory/api/npm/npm-local/:email@example.com //localhost:8081/artifactory/api/npm/npm-local/:always-auth=true
From Artifactory 3.5.3, you can use the following command to get these strings directly from Artifactory:
$ curl -uadmin:password "http://localhost:8081/artifactory/api/npm/npm-local/auth/jfrog"
When using scope authentication, npm expects a valid email address. Please make sure you have included your email address in your Artifactory user profile.
The password is just a base64 encoding of your Artifactory password, the same way used by the old authentication configuration.
While npm scope packages have been available since version 2.0 of the npm command line tool, we highly recommend using npm scope packages with Artifactory only from version 2.1.9 of the npm command line tool.
Automatically Rewriting External Dependencies
Packages requested by the Npm client frequently use external dependencies as defined in the packages'
package.json file. These dependencies may, in turn, need additional dependencies. Therefore, when downloading an Npm package, you may not have full visibility into the full set of dependencies that your original package needs (whether directly or transitively). As a result, you are at risk of downloading malicious dependencies from unknown external resources. To manage this risk, and maintain the best practice of consuming external packages through Artifactory, you may specify a "safe" whitelist from which dependencies may be downloaded, cached in Artifactory and configure to rewrite the dependencies so that the Npm client accesses dependencies through a virtual repository as follows:
- Check Enable Dependency Rewrite in the Npm virtual repository advanced configuration.
- Specify a whitelist patterns of external resources from which dependencies may be downloaded.
- Specify the remote repository in which those dependencies should be cached.
It is preferable to configure a dedicated remote repository for that purpose so it is easier to maintain.
In the example below the external dependencies will be cached in "npm" remote repository and only package from
https://github.com/jfrogdev are allowed to be cached.
When downloading an Npm package, Artifactory analyzes the list of dependencies needed by the package.
If any of the dependencies are hosted on external resources (e.g. on
github.com), and those resources are specified in the white list,
Artifactory will download the dependency from the external resource.
Artifactory will cache the dependency in the remote repository configured to cache the external dependency.
Artifactory will then modify the dependency's entry in the package's package.json file indicating its new location in the Artifactory remote repository cache before returning it to the Npm client.
Consequently, every time the Npm client needs to access the dependency, it will be provisioned from its new location in the Artifactory remote repository cache.
Viewing Individual Npm Package Information
Artifactory lets you view selected metadata of an npm package directly from the UI.
In the Tree Browser, drill down to select the tgz file you want to inspect. The metadata is displayed in the Npm Info tab.
Watch the Screencast
<iframe width="560" height="315" src="https://www.youtube.com/embed/8wYf9unk_Uw" frameborder="0" allowfullscreen></iframe>