Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`package-lock.json` is missing some `resolved` and `integrity` values
See original GitHub issueYour Question
There are two cases in the package-lock.json where the resolved and integrity values are missing:
https://github.com/corona-warn-app/cwa-website/blob/4142215c9b3b742480ba5f3446cbedd7843d7833/package-lock.json#L4372
https://github.com/corona-warn-app/cwa-website/blob/4142215c9b3b742480ba5f3446cbedd7843d7833/package-lock.json#L13274
It appears #1499 made this change, but I could not find any explanation for this. Is there a reason why this was done?
When I run npm install it fills these missing values, but the build succeeds without any (noticable) issues.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the clarification, I will close this issue then.
My changes were indeed unintended; I was rather concerned about updating Cypress and we had no issues from the MR.
I did however update the lockfileVersion from 1 to 2 then back to 1 in this commit https://github.com/corona-warn-app/cwa-website/pull/1499/commits/61e9fcba9572e68fa04f55032290acc2d5a695a8