Update cached licenses and added package-lock

[JeroenKnoops]

Problem

Since the package-lock.json is missing, you're not sure what dependencies are used.
This will result in a mismatch in the cached licenses and the actual licenses.

This results in a failing licenses workflow, see issue #25

Solution

• Add package-lock.json
• Update cached licenses

Related issues

Closes #3, #25

[rodrigoargumedo]

@JeroenKnoops I think adding RUN npm install -g [email protected] or RUN npm install -g npm@latest to the dockerfile should resolve this problem.

[JeroenKnoops]

@JeroenKnoops I think adding RUN npm install -g [email protected] or RUN npm install -g npm@latest to the dockerfile should resolve this problem.

Using @latest can result in the same type of errors in the future.. I would advise against that.

The reason the license check fails is because the cached license files are not matching the actual used dependencies.

I recommend either removing the license check with cached licenses yml files, or use a package-lock.json to make sure the dependencies are pinned.

[dakale]

LGTM, thanks @JeroenKnoops!