The project contain both yarn.lock and package-lock.json. It is recommended to use one package manager and stick to it throughout, to prevent confusion, resolution inconsistencies issues and inconvenience to maintain two unsynchronized lock files. One other option would be to not use any lock management at all if our project always work on latest version of dependencies.
Yarn is recommended to use, since 1.7.0 it is now able to importpackage-lock.json and also we're using nextjs which uses yarn implicitly.
The project contain both
yarn.lockandpackage-lock.json. It is recommended to use one package manager and stick to it throughout, to prevent confusion, resolution inconsistencies issues and inconvenience to maintain two unsynchronized lock files. One other option would be to not use any lock management at all if our project always work on latest version of dependencies.Yarn is recommended to use, since
1.7.0it is now able to importpackage-lock.jsonand also we're using nextjs which usesyarnimplicitly.