JavaScript support FAQs

Search…

Which version(s) of Node do you support?
There are two answers:
1.For docker containers, you can use any version that you wish. Usually you would pull in a source image and version with tag like FROM node:16 at the top of your Dockerfile. Internally, we use NVM and recommend you do as well, see the next option. There is an example to add NVM to your alpine images here.
2.For static build images, we use NVM which will use whatever version you have in an .nvmrc file. You can specify a global version at the top of your build directory and override different versions further down the directory structure as well. Read the docs for more information, or this Stack Overflow answer. Simply create an .nvmrc file with the exact version you wish to use and we will build your project with that version or versions.
Do you support private NPM libraries during build?
Yes, but it might require some additional work on your part. Please read this excellent article for all the technical details which will be described briefly below.
1.Add a .nprmrc file to your code repository with the contents that look something like //registry.npmjs.org/:_authToken=${NPM_TOKEN} Do not actually fill in your token here! Use the variable which will be substituted later (this file is safe to check in to your code version system).
2.Add a Build Argument to your Dockerfile, preferably somewhere near the top (add a comment so you can remember why you put it there too!) The line looks like ARG NPM_TOKEN
3.Add a copy command so the file is copied into your docker container right below the argument, but above the npm install command that you use. The line looks like COPY .npmrc .npmrc
4.Push your changes to Github or Bitbucket on a branch.
5.Make sure you generate (or use an existing) token that is READ-ONLY and can be revoked safely without affecting your other pipelines as best practice. Anyone who is an owner of your ReleaseHub account can see and change these build arguments.
6.Now add a Build Argument in the account settings in the builds tab and add your token to the build arguments. This looks like the next screen:
​
Once you've done these steps, your build should use the NPM token you supplied to pull private libraries. If it works, merge your changes to the default or main development branch for use with your ReleaseHub process.
What About Github packages?
The same applies for most other npm repositories as above. For Github packages, ensure that your token has privileges for ['read:packages']
Also you will want your .npmrc file to look similar to:
//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}
@myorg:registry=https://npm.pkg.github.com/
What about Static Service Deployments?
Instead of adding App-Level Build Arguments, (which do work, but are usually reserved for Docker images), you can instead use regular Environment Variables for ${GITHUB_TOKEN} (and remember to add secret: true for the token).
NPM install works as you described, what about YARN?
The instructions seem to be the same for NPM as described above, but have one extra step to add an additional .yarnrc file for the private repository. Please see this discussion for more details. Please let us know if this works or the documentation can be improved!

Frequently Asked Questions - Previous

Docker support FAQs

Next - Integrations

Integrations overview

Last modified 8d ago

Copy link

On this page

Which version(s) of Node do you support?

Do you support private NPM libraries during build?

What About Github packages?

What about Static Service Deployments?

NPM install works as you described, what about YARN?