prefer npm ci over npm i

[jameswragg]

Re #100

[Nargonath]

The changes LGTM. I tested a npm run build:web locally and it failed. Here is the result:

Not sure what the root cause. I have dug into it.

[jameswragg]

I would guess this to be a mismatch of npm package-lock.json versions.Things to try:1. Re-create your package-lock2. Match local npm versions to the container or,3. Update node base image in DockerfileOn 11 Dec 2023, at 10:20 am, Jonas Pauthier ***@***.***> wrote: @Nargonath commented on this pull request. The changes LGTM. I tested a npm run build:web locally and it failed. Here is the result: image.png (view on web) Not sure what the root cause. I have dug into it. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Nargonath]

Yeah that's what I thought as well. The image is still using node 14 so we should probably upgrade it anyway.

[jameswragg]

@Nargonath do you want me to update the base image in this PR?
If so, the current LTS (20)?

[Nargonath]

Let's separate the concern. I'll merge this one and if you want to open another one to upgrade the base image version, feel free to do so. Thanks 🙏