title: Should I update my npm version or use the one node.js provides?
body: <p>I have a project that uses node.js 14.16.0. Both me and my teammember use that version.
  I use npm 6.14.11 and my teammember uses npm 7.x.x.
  This results in the package-lock.json being different; the <code>lockFileVersion</code> property is 1 on my PC but 2 on theirs.</p>
  <p>I already use <code>nvm</code> and am considering to add a <code>.nvmrc</code> so everyone always uses the same node version, but this doesn't fix the npm version issue.</p>
  <p>I believe that it is a good idea to use the npm version that the installed node.js version provides. If the next big LTS release uses a new npm version, the project will switch to that. But on <a href="https://www.npmjs.com/get-npm" rel="noreferrer">NPM's site</a> they say:</p>
  <blockquote>
  <p>npm is a separate project from Node.js, and tends to update more frequently. As a result, even if you’ve just downloaded Node.js (and therefore npm), you’ll probably need to update your npm. Luckily, npm knows how to update itself!</p>
  </blockquote>
  <p>Which makes me believe I should always update.</p>
  <p>But they also say:</p>
  <blockquote>
  <p>Node.js has lots of versions! To use Node.js, and therefore npm, effectively, you’ll want to make sure that you are on a version that is supported by the Node.js team. In general, you should use the version of Node.js labelled “LTS”.</p>
  </blockquote>
  <p>Which makes me believe I shouldn't update and just use the one node.js provides.</p>
  <p>What is the best practice?</p>