Start Building for Free

Publish to NPM registry

5 months ago1 min read
Server v4.x
Server v3.x
On This Page

In this how-to guide, you will learn how to configure CircleCI to publish to the NPM registry.


Setting up CircleCI to publish packages to the npm registry makes it easy for project collaborators to release new package versions in a consistent and predictable way.

1. Obtain the npm authToken

Obtain the npm authToken for the account that you wish to use to publish the package. You can do that by logging in to npm (npm login). This will save the authToken to the ~/.npmrc file. Look for the following line:


In this case, the authToken is 00000000-0000-0000-0000-000000000000.

2. Set NPM token

Go to your project settings, and set the NPM_TOKEN variable to the obtained authToken.

3. Configure CircleCI

Configure CircleCI to add the authToken to ~/.npmrc, run npm publish and only for versioned tags:

version: 2.1

      - image: <docker-image-name-tag>
      - checkout
      - run:
          name: Publish to NPM
          command: |
            npm set //$NPM_TOKEN
            npm publish

      - publish:
              only: /v[0-9]+(\.[0-9]+)*/

4. Create a new version

When you want to publish a new version to npm, run npm version to create a new version:

npm version 10.0.1

This will update the package.json file and creates a tagged Git commit. Next, push the commit with tags:

git push --follow-tags

5. Publish

If tests passed, CircleCI will publish the package to npm automatically.

Help make this document better

This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.

Need support?

Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.

You can also visit our support site to find support articles, community forums, and training resources.