Gitlab

... about GitLab Caches and Artifacts (and which to use for node_modules)

When you deploy a NodeJS application with GitLab, one of the first steps is the installation of the dependencies. Many subsequent pipeline jobs will depend on the installation result, which is the node_modules folder (or several folders).

GitLab jobs, however, runs completely independent from each other and don’t share any resulting output by default. So how can subsequent jobs use the node_modules folder?

In GitLab there are two ways to hand over files to other jobs: Artifacts and Caching. Here are some of the basic characteristics.

... A Number of Things about Gitlab Ci and Npm

Recently I had to add a semi-complex TS application to quite-complex GitLab CI/CD pipeline.

Here are a number of resources that helped me understand some of the peculiarities of running npm inside GitLab:

• GitLab Cache and Artifacts explained
• A StackOverflow post on npm/GitLab
• GitLab docs: How to use references