Closed jsumners-nr closed 5 months ago
yea we should update to prevent this issue in the future. here's the workflow
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
a26cc3d
) 80.07% compared to head (c1af1b9
) 80.07%.:exclamation: Current head c1af1b9 differs from pull request most recent head ceb7018. Consider uploading reports for the commit ceb7018 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@bizob2828 I have addressed your feedback, but I'm rather confident it will not solve the issue going forward. I believe the problem is npm install <pkg>
isn't updating package-lock.json
locally (could be due to a config I have on my system).
What benefit does the package-lock.json
provide us anyway? It doesn't get read when the module is installed because package managers ignore transitive lock files.
Proposed Release Notes
Links
Details