What is the point of having resolved URL in package-lock.json? : <p>whenever I generate a package-lock file, there is also "resolved" block that looks like this:</p>

<pre><code>"resolved": "http://devel.npm.registry:4873/lodash/-/lodash-4.17.5.tgz"
</code></pre>

<p>What is the point of this URL? Later, if I try to install dependencies based on this package-lock, do I need to use the same npm registry? Because we use a different npm registry for local development and for production builds. Thus when I develop, I use <code>devel.npm.registry</code>, but the CI tool uses <code>production.npm.registry</code>. According to my tests, the URL doesn't matter (I tried <code>npm@6.4.1</code>). But it is current implementation that's gonna change soon or is the URL intentionally ignored? I have the feeling that some of the previous versions of npm actually checked the resolved URLs. </p>

<p>The <a href="https://docs.npmjs.com/files/package-lock.json#resolved" rel="noreferrer">documentation</a> isn't much helpful in this case.</p>
