4 ms·
Not that this is a showstopper, but I have issues with the package-lock.json file where the `resolved` field (the package's registry URL) constantly flip flops
by dhritzkiv 8y ago
Not that this is a showstopper, but I have issues with the package-lock.json file where the `resolved` field (the package's registry URL) constantly flip flops between http and https protocols, depending on which machine I'm on (home, work, or docker container), whenever I run `npm install`. Sounds not so bad, but it becomes a mess in git, and causes any docker build caches to become invalidated.
- scrollaway 8y agoThat sounds pretty bad and I'm not so sure it's a npm bug. Do you have a diff of the change in question? Is it on the npm registry or a custom one?
- dhritzkiv 8y agoIt's on the npm registry, affecting the npm client: https://npm.community/t/some-packages-have-dist-tarball-as-http-and-not-https/285/51 https://npm.community/t/some-packages-have-dist-tarball-as-h...
- jwalton 8y agoA very similar bug that we run into sometimes: https://npm.community/t/npm-install-or-npm-update-turns-a-bunch-of-resolved-in-package-lock-json-from-real-values-to-false/3308 https://npm.community/t/npm-install-or-npm-update-turns-a-bu...
- whatever_dude 8y agoOh man, I get that all the time, hate it so much.