yarn vs npm

I usually have to start the container with --force-recreate because Nitro(?) apparently doesn't clean up properly when shutting down (described in this issue (there is also a Nuxt-Docker setup dealing with this problem at the end there)). During the start-up phase I then always get this warning:

informationportal_frontend_dev    | yarn install v1.22.19
informationportal_frontend_dev    | warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

I then also get an automatically generated yarn.lock file which I think I would have to untrack or delete before committing something. What do you think about this @gabriel.preuss? Should we replace package-lock.json with yarn.lock?