-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm integrity check background-geo-location #158
Comments
Hm... This hash could be a remnant from an earlier version of installing the dependency that has never been updated in the |
If I now run One solution to this would thus be to push the new
|
I just tried out your fix and get a number of warnings. Do you get similar ones?
|
My current setup is
npm install finishes for this branch, there are however still some warnings:
|
after some more testing with @zven, it turns out that npm calculated different hash values for noerw's fork of |
The integrity field/hash value for the background-geo-location plugin saved in package-lock.json does not correspond to the hash of the package that is being installed by npm.
Steps to reproduce:
This results in the following error:
The text was updated successfully, but these errors were encountered: