NPM package issues commands

npm WARN old lockfile

npm WARN old lockfile The package-lock.json file was created with an old version of npm

There are several ways to deal with this:

  1. Ignore it. It’s just a warning and does not affect the installation of modules.
  2. Run npm ci to make sure your node_modules reflects the lock file, then remove package-lock.json, and then run npm install (with the newer version of npm) to regenerate a package-lock.json. Because everything in node_modules will meet all the requirements, the only change from npm install will be a newly-generated package-lock.json file. Commit the updated version of package-lock.json to the repo/Docker image or whatever.
  3. Downgrade npm to an older version in production. Consider running npm version 6 as that is what ships with the current (as of this writing) LTS version of Node.js. In the case being asked about in this question, I imagine you can just leave out the RUN npm -g install npm@7.19.1 from the Dockerfile and instead use the version of npm that is installed with the Docker image (which in this case will almost certainly be npm@6 since that is what ships with Node.js 14.x).
  4. If you want to run one command with an older […]