docker-web container ignoring package-lock.json causing version conflicts

[FWest98]

At the moment, the web module cannot be built since npm install encounters the following issue:

7.788 npm error code ERESOLVE
7.788 npm error ERESOLVE unable to resolve dependency tree
7.788 npm error
7.788 npm error While resolving: @dodona/dolos-web@2.9.2
7.788 npm error Found: vite-plugin-vuetify@1.0.2
7.788 npm error node_modules/vite-plugin-vuetify
7.788 npm error   dev vite-plugin-vuetify@"^1.0.2" from the root project
7.788 npm error
7.788 npm error Could not resolve dependency:
7.788 npm error peerOptional vite-plugin-vuetify@">=2.1.0" from vuetify@3.8.1
7.788 npm error node_modules/vuetify
7.788 npm error   dev vuetify@"^3.7.3" from the root project
7.788 npm error   peer vuetify@"^3.0.0-beta.4" from vite-plugin-vuetify@1.0.2
7.788 npm error   node_modules/vite-plugin-vuetify
7.788 npm error     dev vite-plugin-vuetify@"^1.0.2" from the root project
7.788 npm error
7.788 npm error Fix the upstream dependency conflict, or retry
7.788 npm error this command with --force or --legacy-peer-deps
7.788 npm error to accept an incorrect (and potentially broken) dependency resolution.
7.788 npm error
7.788 npm error
7.788 npm error For a full report see:
7.788 npm error /root/.npm/_logs/2025-04-14T12_02_54_208Z-eresolve-report.txt

I think it would be nice to also include a package-lock.json file in the repository, so prevent such conflicts from magically arising in the future.

[rien]

This is indeed a problem I've noticed with the web docker image.

We do have top-level package-lock.json because we're working with NPM workspaces. However, this does not work with the docker image.

I would rather avoid having a second package-lock.json in the web project, as there is change the two lock files might grow inconsistent at some point.

There seem to exist some solutions to generate the package-lock.json automatically (see npm/rfcs#554 (comment)), but I will need to dig deeper on this.