Note: I am porting this issue over from the now archived npm.community with the hopes that this issue can get escalated and resolved as it looks like it has been largely overlooked up to this point. Maybe this issue can be set to resolved: true 😉

What / Why

• My package-lock.json constantly toggles between:

 "resolved": "https://registry.npmjs.org/tar/-/tar-4.4.1.tgz",
  "resolved": false,

When

• n/a

Where

• n/a

How

Current Behavior

• Running npm install or npm update sometimes trashes the lockfile, setting resolved: false for a number of packages.

Steps to Reproduce

• Run npm install or npm update
• Check package-lock.json for changes

Expected Behavior

• resolve does not switch between false and the URL.

Who

• n/a

References

• https://npm.community/t/constant-resolved-false-toggle/276
• package-lock.json file has erroneous resolved = false fields RocketChat/Rocket.Chat#15408
• https://npm.community/t/npm-install-or-npm-update-turns-a-bunch-of-resolved-in-package-lock-json-from-real-values-to-false/3308
• Updating End Date Field on Campaign Page DoSomethingArchive/rogue#974 (comment)