Description:

The package-lock.json file contains lines of the form

Where the resolved field doesn't actually point to the resolved URI, but is just false. This prevents certain tools, such as node2nix in my case, from being able to use the lock file to fully resolve dependencies.

I found this issue which mentions such a problem: https://npm.community/t/npm-install-or-npm-update-turns-a-bunch-of-resolved-in-package-lock-json-from-real-values-to-false/3308, but without any good solutions other than rm -rf node_modules && npm install.

It would be great if this problem could at least be temporarily fixed on the 2.0.0 release branch.

Expected behavior:

package-lock.json should point all resolved fields to URI's

Actual behavior:

Some URI's are false