Gitlab Deployment w/ NPM Private Package *

https://webbureaucrat.gitlab.io/posts/continuously-deploying-an-npm-package-with-gitlab-ci-cd/

Setting up continuous deployment is important to me, even when publishing is as simple as it is on npm. The official GitLab documentation, though, is a little more than I need and geared toward their own npm repository, so I’d like to gather the information I need here in a brief article.

Generate and store an authentication token

The npm team has made this straightforward.

Generating the token in npm
Go to npmjs.com and log in if you haven’t already.
Click on your profile picture at the top right.
Select the fifth item, “Access Tokens.”
Click “Generate New Token” on the top right of the page.
Select the middle option, “automation” for the right security settings.
Click “Generate Token.”
Copy the token to your clipboard.

Storing the token in GitLab

Log into GitLab and open the project you intend to automate.
Select “Settings” at the bottom of the menu on the left. This will open a submenu.
Select “CI/CD.”
Find the “Variables” section of the CI/CD menu and click “expand” on the right.
Click the green “Add variable” button at the bottom.
Fill in the “Key” text box with “NPM_TOKEN”.
Fill in the “Value” box with the token you copied from earlier.
Make sure the “Type” is set to “variable” instead of “file.”
Make sure both checkboxes are checked to protect and mask the variable.

A word on security
Clearly, an authentication token, especially one that controls deployment to production, is very sensitive information, so it’s worthwhile to familiarize oneself with the protections GitLab offers.

Masking an environment variable protects the variable from being seen in the console output. It is easy to imagine a scenario where an error message (or just a simple scripting mistake) could lead to this kind of information being printed to the console, and once the toothpaste is out of the tube and on the internet, there’s no putting it back in–you have to revoke that token and generate a new one. Masking prevents this easy-to-make security mistake.

Protecting an environment variable is a kind of access control. A protected environment variable can only be used in protected branches or on protected tags, and it can’t be seen by all contributors.

A critically sensitive authentication token like an NPM publish token should be both protected and masked.

Set up the pipeline with your .gitlab.yml

This is the easy part. Copy the following text and save it to a file called

.gitlab.yml

image: node:latest
stages:
  - deploy

deploy:
  stage: deploy
  script:
    - echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > .npmrc
    - npm publish

Version 2 of .gitlab.yml addtions

build_job: 
  script:
  - printenv NPM_TOKEN
  - npm config set //registry.npmjs.org/:_authToken ${NPM_TOKEN}
  - npm i @falconstudios/ns-player

Just to break it down: This file grabs an image that has node installed. It deploys by creating a file called .npmrc that defines where our registry is and what our authentication token is based on the environment variable NPM_TOKEN we created earlier. With that file in place, npm publish will run.

Celebrate
Update your package.json with a fresh version number to make sure the push succeeds, then commit and push the new .gitlab.yml and the edited package.json. The pipeline will succeed every time you increment the version number.